[Date Prev][Date Next]
Re: Got it working
At 08:03 AM 2002-02-15, manig wrote:
>- Added a password for the user using saslpasswd(8), with the following
>saslpasswd -c "u:shigeru"
It seems odd that you have authentication identities which
start with "u:". You are likely confusing the form of LDAP
authorization identity derived from authentication identities
with the authentication identities.
If you represent the authentication identity "u:shigeru"
as LDAP authorization identity, it would become "u:u:shigeru".
I suggest you use the authentication identity "shigeru"
instead, which when represented as the LDAP authorization
identity would be "u:shigeru".
>- Things should be working properly now. Test things out:
>/usr/local/bin/ldapsearch -I -D "uid=shigeru" "cn=*"
Since you are doing SASL authentication, the DN here is irrelevant.
>SASL/DIGEST-MD5 authentication started
>Please enter your authentication name: u:shigeru
>Please enter your authorization name: u:shigeru
This says I am "u:shigero" (LDAP authzid "u:u:shigeru") but
I'd like to be authorized as "u:shigeru". Whether the
LDAP authzid "u:u:shigeru" has permission to authorize as the
LDAP authzid "u:shigeru" is generally a matter of policy.
In 2.0, there is no policy support and would normally
refuse to accept this bind. However, as allows the
authentication identity "bob" to authorize as the
authorization identity "u:bob" or as the INVALID
authorization identity "bob" (for historical reasons).
To explain the behavior you see, s/bob/u:shigeru/ in the above.
>Note that I entered u:shigeru as both the authentication and
>authorization names. This causes whichever OpenLDAP client (in this case
>ldapsearch) to not specify an authzid in the DIGEST-MD5 authentication
>process (which is good). If I leave authorization name blank, it will
>specify authzid="", which is less desirable. I don't know if this should
>be considered a bug.
Unless you are attempting proxy authorization, an authorization
should not be specified. To do so unnecessarily will only cause