Shibboleth IDP 3 Multiple Username Logins

[Juan Quintanilla]

Hi Scott,


Sorry about that, my question would be what is the best approach configuring shibboleth so that it can authenticate the same user with multiple usernames values?


For example:

 User john Doe has 2 different usernames in different OU's on Ldap and they are both unique, the authentication  piece searches both OU's so there is no problem there with authentication.  So if we want to give the user the ability to also authenticate with their numerical ID we would run into problems with it returning multiple results due to the fact that this users numerical ID is the same for both his usernames.


How can we limit the results returned to the first successful entry and then go about resolving that numerical ID to their respective username instead?


I greatly appreciate any input.


Thanks for your help.



___________________
Juan Quintanilla
Enterprise Systems Group
305-348-6573
jquin014 at fiu.edu<mailto:jquin014 at fiu.edu>


________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Wednesday, August 17, 2016 11:28 AM
To: users at shibboleth.net
Subject: Re: Shibbboleth IDP 3 Multiple Username Logins

On 8/17/16 11:15 AM, Juan Quintanilla wrote:
>
> We are currently running Shibboleth IDP 3  using ldap for
> authentication.  We would like to be able to have users login with both
> their username (ex: jdoe) as well as their numerical username (ex:
> 1111111) but resolving that value back to their regular username
> (jdoe).   Has anyone using shibboleth dealt with authenticating
> different usernames for a user?

Yes. I'm not sure of your question. There's a whole
SubjectCanonicalization subsystem now devoted to providing a lot of
options for how to deal with that after the fact.

-- Scott
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160817/4f71c70d/attachment.html>