You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Josh Thompson (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/03 22:08:21 UTC
[jira] [Resolved] (VCL-319) API LDAP authentication problem with
servers where DN must be looked up
[ https://issues.apache.org/jira/browse/VCL-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Thompson resolved VCL-319.
-------------------------------
Resolution: Fixed
The code for authenticating API users was fixed in r1309118, but I forgot to tag the commit with this JIRA issue.
Due to the difference in exit/return codes, separating this out into its own function is not really worth it. So, I'm going to leave separate implementations of it.
> API LDAP authentication problem with servers where DN must be looked up
> -----------------------------------------------------------------------
>
> Key: VCL-319
> URL: https://issues.apache.org/jira/browse/VCL-319
> Project: VCL
> Issue Type: Sub-task
> Components: web gui (frontend)
> Affects Versions: 2.1
> Reporter: Josh Thompson
> Assignee: Josh Thompson
> Priority: Minor
> Fix For: 2.3
>
>
> Authentication for the API doesn't handle LDAP servers where the user's full DN must be looked up before doing an LDAP bind to authenticate the user. The code for that for normal authentication should be separated out so that it can be called for normal logins and for API logins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira