> Marvin, could you explain a little more how you have implemented your Our solution leverages the ability of CAS 3.3.x to send arbitrary attributes about the authentication principal back to CAS clients in a SAML payload. CAS clients may request SAML by validating service tickets at the /samlValidate URI. Although LOA is truly an authentication attribute, there is no method currently for transmitting authentication attributes to CAS clients, which explains our decision to treat LOA as a principal attribute for the time being.
Hope that gives a high level overview of our solution. If you wish to do something similar, I'd recommend code review at this point. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
