[Date Prev][Date Next]
(ITS#6456) Feature Request
Submission from: (NULL) (22.214.171.124)
Having found out this doesn't already exist as another parameter or
configuration method, I am hereby submitting a request for a particular
When performing idassert-bind operations, such as with back_ldap, it would be
great if an option could be added which would allow specific matched client DNs
to be matched and asserted as usual (e.g: the anonymous user asserting to a
backend "proxyauthenticator" account) .... while other clients (flagged somehow)
would pass-through as themselves.
Example (as I might do it for my purposes):
# anonymous clients will assert as "proxyauthenticator", since the backend may
not allow anonymous binds.
# this guy will pass through as himself to the backend, as-is.
This would be really helpful, not sure if its difficult to implement ...