Try doing two ldap entries. It will search for phone first, if not found
will search using email next
cas.authn.ldap[0].type=AUTHENTICATED
cas.authn.ldap[0].ldapUrl=
cas.authn.ldap[0].connectTimeout=5000
cas.authn.ldap[0].baseDn=
cas.authn.ldap[0].userFilter=(telephoneNumber={user})
cas.authn.ldap[0].subtreeSearch=true
cas.authn.ldap[1].type=AUTHENTICATED
cas.authn.ldap[1].ldapUrl=
cas.authn.ldap[1].connectTimeout=5000
cas.authn.ldap[1].baseDn=
cas.authn.ldap[1].userFilter=(email={user})
cas.authn.ldap[1].subtreeSearch=true
On Thursday, May 24, 2018 at 11:25:29 AM UTC-7, John D Giotta wrote:
>
> I have this requirement where we're supposed to allow users to sign-in
> with either an email address or a phone number.
>
> 1) Can I tailor CAS for either of those 2 options?
>
> 2) When it comes to attributes, how do I pair that user (because the user
> id is different) with the attributes clause?
>
>
>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/0b5a3364-c534-4638-9f1c-122716e9d7d5%40apereo.org.
