CAS users would authenticate (query a user base) with many different persistent user stores using many different authentication methods, they may have different needs for user attributes. I've seen many requests for ways to throw in or add on an attribute to something already in existence.
I have questions around the use of these attributes. E.g. are the attributes to assist in the authentication process or some other reason. I listed several specific questions below and I'm very interested in your responses to them. 1. Is the future intention to query for user attributes, find them, and CAS then return them in some fashion to assist in the validation of credentials, authentication, etc.? 2. Is the intention to query for user attributes at the CAS server as a REST call and a stand-alone request? 3. Are user attribute requests to be a 1) service or 2) an extension of an existing CAS authentication request 4. Does CAS ever intend to provide the persistence of identities, their credentials, and their attributes? I.e. does the CAS community wish that CAS handled everything, including the identity management? 5. Have these questions been asked before? 6. Is there a community desire to reduce the number of CAS authentication options? David _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
