Hi Clément,
There is a firewall in between, yes. But ldap ports (389 and 636) are opened so
it shouldn't be an issue here. I will try to test the connection bypassing the
FW just to be sure though.
I am not using ldapsearch here but with Apache Directory Studio, it works
perfectly fine, at lea
Hi Clément,
This is what I get when I set the timeout to 10sec.
So you are right, LSC expects something but doesn't get an answer...
sept. 19 11:08:21 - ERROR - Error while looking for (cn=TEST TEST) in cn=PBX0:
javax.naming.CommunicationException: Request: 2 cancelled; remaining name ''
Clément,
Sorry to spam you with my posts but, I tried to search through the directory
using ldapsearch:
ldapsearch -h xxx.xxx.xxx.xxx -p 389 -b -x -D "test" -w "test" -b "cn=PBX0"
"cn=*"
And I get the correct results:
[...]
# TEST, PBX0
dn: cn=TEST,cn=PBX0
cn: TEST
e164: 3445
pbx::
Dear all,
The symptom:
An ldap user object in the source DIT is built around the Structural
ObjectClass :inetOrgPerson.
When the user leaves the organisation then the deprovisioning process
requires her/his ldap object to change to a new form which is now built
around a new Structural Objec
2016-09-19 7:20 GMT-04:00 Nikos Voutsinas :
> Dear all,
Hello Nikos,
>
> The symptom:
>
> An ldap user object in the source DIT is built around the Structural
> ObjectClass :inetOrgPerson.
>
> When the user leaves the organisation then the deprovisioning process
> requires her/his ldap object to
2016-09-19 8:27 GMT-04:00 Bruno MORAZZONI :
> Hello Clément,
>
> Last post for today, I promise!
> From the printscreen below, on the left, the trace from Apache Directory
> Studio.
> On the right, the trace from LSC.
>
> The only difference is the controlType line : would it explain why the
> LDA
Hi There:
We have a directory structure -- which correlates to a Library index naming
convention -- where the parent, and immediate child, may have the same name.
Example:
Location>Stack>Topic>example.com
'Location' and 'example.com' are static.
Samples;
Foobar>Physics>Physics>example>com
Foo
"When running LSC, the OUs for the 'Stack' tier are created as long as the
immediate child OU - i.e. 'Topic' -- does not share the same name."
My apologies -- I meant to say the 'Topic' OU tier is created as long as it
does not share same name as the parent OU (i.e. the 'Stack' tier).
Any ideas o
Many thanks for your help Clément, it works like a charm now!
Le 19 septembre 2016 à 15:32, Clément OUDOT a écrit :
2016-09-19 8:27 GMT-04:00 Bruno MORAZZONI :
Hello Clément,
Last post for today, I promise!
From the printscreen below, on the left, the trace from Apache Directory S
2016-09-19 12:36 GMT-04:00 Joel Levin :
> "When running LSC, the OUs for the 'Stack' tier are created as long as the
> immediate child OU - i.e. 'Topic' -- does not share the same name."
>
> My apologies -- I meant to say the 'Topic' OU tier is created as long as it
> does not share same name as th
10 matches
Mail list logo