You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Bart Coninckx <ba...@telenet.be> on 2013/02/08 21:07:05 UTC
OM does not bind with full DN
Hi All,
am configuring OM 2.1 for Novell eDirectory. To troubleshoot I'm
sniffing everything happening on the LDAP server.
This is the sequence of things
1. bind with admin DN (you see the full DN)
2. search for what was entered as userfield with the property in the
LDAP file for "field_user_principal"
3. you see the search result with the full DN
4. authentication of the user.
Step 4 goes wrong however: I see OM trying to authenticate with only the
username, and not the full DN.
Is this a bug?
Cheers,
BC
Re: OM does not bind with full DN
Posted by Bart Coninckx <ba...@telenet.be>.
Seems very similar to
http://markmail.org/message/jgkeonu3kzqgm4nv#query:+page:1+mid:4swrd7jq5ozf6e3x+state:results
So this does not work for OpenLDAP either. But since ldap_server_type is
set to "OpenLDAP", the full DN should be used for binding, however, it
does not with my install
(apache-openmeetings-2.1.0.r1441250-31-01-2013_2314.tar.gz)
It is supposed to be fixed in
https://issues.apache.org/jira/browse/OPENMEETINGS-144
but I still seem to have problems with it.
BC
On 02/08/13 21:35, Bart Coninckx wrote:
> In partial reply to my own question: I suppose the "domain" field is
> created for the purpose of constructing a full user name to bind with.
> But for eDirectory this does not work, one needs to be able to bind
> with the full DN.
>
> Cheers,
>
> BC
>
>
> On 02/08/13 21:07, Bart Coninckx wrote:
>> Hi All,
>>
>> am configuring OM 2.1 for Novell eDirectory. To troubleshoot I'm
>> sniffing everything happening on the LDAP server.
>>
>> This is the sequence of things
>>
>> 1. bind with admin DN (you see the full DN)
>> 2. search for what was entered as userfield with the property in the
>> LDAP file for "field_user_principal"
>> 3. you see the search result with the full DN
>> 4. authentication of the user.
>>
>> Step 4 goes wrong however: I see OM trying to authenticate with only
>> the username, and not the full DN.
>>
>> Is this a bug?
>>
>>
>> Cheers,
>>
>>
>> BC
>
Re: OM does not bind with full DN
Posted by Bart Coninckx <ba...@telenet.be>.
In partial reply to my own question: I suppose the "domain" field is
created for the purpose of constructing a full user name to bind with.
But for eDirectory this does not work, one needs to be able to bind with
the full DN.
Cheers,
BC
On 02/08/13 21:07, Bart Coninckx wrote:
> Hi All,
>
> am configuring OM 2.1 for Novell eDirectory. To troubleshoot I'm
> sniffing everything happening on the LDAP server.
>
> This is the sequence of things
>
> 1. bind with admin DN (you see the full DN)
> 2. search for what was entered as userfield with the property in the
> LDAP file for "field_user_principal"
> 3. you see the search result with the full DN
> 4. authentication of the user.
>
> Step 4 goes wrong however: I see OM trying to authenticate with only
> the username, and not the full DN.
>
> Is this a bug?
>
>
> Cheers,
>
>
> BC