Shibboleth IDP 3 Multiple Username Logins
IAM David Bantz
dabantz at alaska.edu
Wed Aug 17 15:06:13 EDT 2016
Something like this in a jaas.config (multiple directories each with both
OUs)
// first OU
org.ldaptive.jaas.LdapLoginModule sufficient
ldapUrl="ldap://ldap1.tld:3268 ldap://ldap2:3268"
baseDn="ou=OU1,dc=ldap,dc=tld"
bindDn="cn=..."
bindCredential="••••••••••••••••••••"
sslSocketFactory="{trustCertificates=file:/opt/shibboleth-idp/trustedservercerts/...}"
ssl="false"
tls="true"
userFilter="(|(sAMAccountName={user})(employeeNumber={user}))"
;
// second OU
org.ldaptive.jaas.LdapLoginModule sufficient
ldapUrl="ldap://ldap1.tld:3268 ldap://ldap2:3268"
baseDn="ou=OU2,dc=ldap,dc=tld"
bindDn="cn=..."
bindCredential="••••••••••••••••••••••••"
sslSocketFactory="{trustCertificates=file:/opt/shibboleth-idp/trustedservercerts/...}"
ssl="false"
tls="true"
userFilter="(|(sAMAccountName={user})(employeeNumber={user}))"
;
On Wed, Aug 17, 2016 at 9:11 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 8/17/16 1:05 PM, Juan Quintanilla wrote:
> >
> > So If we setup multiple authentication handlers on Shibboleth, is there
> > a way to tell it to stop processing the other authentication handlers
> > once a match is found?
>
> There are no authentication handlers in Shibboleth, unless you mean
> something internal to the LDAP flow, which I can't answer.
>
> If you mean login flows, it can't work like that when there's user input
> involved, so I doubt that's what you're referring to.
>
> David's JAAS suggestion is valid, since JAAS would cascade attempts
> within a configuration, and the IdP can cascade attempts to try
> different JAAS configurations also. All of that assumes JAAS, and not
> native LDAP.
>
> -- 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/0cd499e9/attachment.html>
More information about the users
mailing list