use Net::LDAP; use Net::LDAP::Control::ProxyAuth; $ldap = Net::LDAP->new( "ldap.mydomain.eg" ); $auth = Net::LDAP::Control::ProxyAuth->new( authzID => 'dn:cn=me,ou=people,o=myorg.com' ); @args = ( base => "cn=subnets,cn=sites,cn=configuration,$BASE_DN", scope => "subtree", filter => "(objectClass=subnet)", callback => \&process_entry, # Call this sub for each entry control => [ $auth ], ); while (1) { # Perform search my $mesg = $ldap->search( @args ); # Only continue on LDAP_SUCCESS $mesg->code and last; }
It allows a client to be bound to an LDAP server with its own identity, but to perform operations on behalf of another user, the "authzID".
With the exception of any extension that causes a change in authentication, authorization or data confidentiality, a single "Proxy Authorization Control" may be included in any search, compare, modify, add, delete, or moddn or extended operation.
As required by the RFC, the criticality of this control is automatically set to TRUE in order to protect clients from submitting requests with other identities than they intend to.
Please note: Unfortunately the OID and the encoding or the "Proxy Authorization Control" changed significantly between early versions of draft-weltman-ldapv3-proxy-XX.txt and the final RFC. Net::LDAP::Control::ProxyAuth tries to cope with that situation and changes the OID and encoding used depending on the constructor argument.
With "proxyDN" as constructor argument the old OID and encoding are used, while with "authzID" as constructor argument the new OID and encoding are used. Using this logic servers supporting either OID can be handled correctly.
Please report any bugs, or post any suggestions, to the perl-ldap mailing list <perl-ldap@perl.org>