We just have separate accounts in AD, which is where we are authenticating and doing attribute release from. The IAM system is responsible for correctly populating the directory and end application if needed in the correct way for each account. This requires multiple accounts and passwords, and currently multiple Duo setups. Although, thinking of it now, we could use alternate usernames on Duo to use the same configuration between different accounts.
On Mon, 2020-05-18 at 10:19 -0700, [email protected] wrote: > At our university, we have some applications where one person will > only have one account and the application is aware of the different > "roles" a person might have, i.e., student, staff, faculty and/or > alumni. We also have some other applications where a person may > have a student account and also a faculty/staff account. Due to > historical reasons, our CAS is built around the former, one-person- > to-one-account model. Up until now, we've a been able to handle > multiple accounts via separate login URLs to the same service, and > CAS will respond with the appropriate staff or student attributes. > > We're now integrating with some Cloud services and the separate login > URL does not appear to be a possibility. We'll just have one URL for > the Cloud service. > > How are other organizations handling this? I'd love to hear some > ideas. > > I can think of a couple ways, but I'm not sure I like them. > > Thank you very much, > Mike -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/792d3a4e0fe3167f3ec9f165b8e6ead0744d9a71.camel%40ndsu.edu.
