Yes, we have the following setup:
The functional account which makes the bind:
AuthLDAPBindDN "CN=ldapagent,OU=Benutzer,OU=_***,DC=***,DC=***,DC=***"
AuthLDAPBindPassword ********
And we have the server URL with filter:
AuthLDAPURL
"ldap://ldap-proxy.***.de:389/DC=***,DC=***,DC=***?sAMAccountName?sub?(objectClass=user)"
Actually one would only need 2 additional fields for the functional
account/password in the LDAP Auth setup, but we do not have the resources right
now for patching Geoserver. I would fin both LDAP Auth mechanisms nice being
supported in the future,
Thomas
Well, then a change to the code is needed to realize your desidered behaviour.
I think you would need to specify:
- the fixed account credentials used to bind
- the filter to use for authentication (I think we could reuse the "filter
used to lookup user" that is present on 2.4); do you have an example of filter
that you use for authentication on the ldap proxy?
It's not trivial, but not that hard to implement.
If you wish to add have it implemented I think you have some options:
- try to create a patch yourself and issue a pull request
- sponsor someone to implement it for you
Mauro
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
