Colin,
I was thinking the user would enter their home organization rather than the auth provider.
CAS should step through different authentication mechanisms in the order they are listed [in config] until it finds a match or exhausts all mechanisms. We use multiple LDAP entries that differ only in the tree searched. I have not tried other mechanisms
like Radius, but it may still apply.
If the above does not work, yes you could insert some Java LDAP calls.
Ray
On Mon, 2019-12-16 at 13:22 -0500, Colin Ryan wrote:
Ray,
Thanks for the response. Issue I see with this is I don't want to have to rely on user input to start this all off. I need to avoid is having a user to find a way to successfully validate via say AuthProvider A (i.e. LDAP), when
I in fact needed them to Authenticate via Provider B (i.e. Radius). Unless I missing something, depending on the user to provide the input required for such a decision is not desirable.
Unless your simply pointing me into a direction where I could insert some Java LDAP calls as I receive the incoming UserID, and then dynamically adjust the Authentication Provider to user for the actual Auth.
Cheers
Sorry to be so unclear. It's all so obvious with different URL/Services, but I'm basically trying to manage a centralized administrative tool overlaying what is essentially a multi-tentant'ed User Database, and CAS's contexts are
so service focused.
Colin