[JIRA] Closed: (SIDP-541) Principal string defined in DataConnector is modified to lower case for authentication causing login problems
Chad La Joie (JIRA)
noreply at shibboleth.net
Thu Feb 23 18:52:37 GMT 2012
[ https://issues.shibboleth.net/jira/browse/SIDP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chad La Joie closed SIDP-541.
-----------------------------
Resolution: Invalid
LDAP principals are case insensitive.
> Principal string defined in DataConnector is modified to lower case for authentication causing login problems
> -------------------------------------------------------------------------------------------------------------
>
> Key: SIDP-541
> URL: https://issues.shibboleth.net/jira/browse/SIDP-541
> Project: Shibboleth IdP 2 - Java
> Issue Type: Bug
> Components: Attribute Resolution
> Affects Versions: 2.3.5
> Environment: Win7 64bit
> Reporter: sdwarfs at idp.protectnetwork.org
> Assignee: Chad La Joie
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Let's assume the following DataConnector definition (in attribute-resolver.xml):
> ----
> <resolver:DataConnector id="myLDAP" xsi:type="dc:LDAPDirectory"
> ldapURL="ldap://ldap.example.org"
> baseDN="ou=people,dc=example,dc=org"
> principal="uid=myService,ou=system"
> principalCredential="myServicePassword">
> <dc:FilterTemplate>
> <![CDATA[
> (uid=$requestContext.principalName)
> ]]>
> </dc:FilterTemplate>
> </resolver:DataConnector>
> In that case the Shibboleth IdP would try to authenticate as "uid=myservice,ou=system" (note the lower case "s" in "myservice").
> This causes the authentication to fail.
> Note: You should also check user authentication process (I did not so far) for the same problem. Meaning: uppercase letters in "uid" entered at single sign on in the browser...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list