I've implemented an option for the CAS 3.0 protocol to allow/disallow the return of custom attributes, as well as fixed typos in some of your methods regarding the spelling of the word "Validate".
This change would allow authentication workflows that occur over the CAS 3.0 protocol to return the custom attributes specified in the CAS configuration to the client by default. As in many cases additional custom mapped attributes are stored there, like first name, last name, phone numbers, etc.
In the event that sensitive information is being sent over this context, returning the attributes can be disabled.
Please let me know if you have an issues with this implementation or would like to discuss further. There may be arguments to having this feature default to false instead of true.
I've implemented an option for the CAS 3.0 protocol to allow/disallow the return of custom attributes, as well as fixed typos in some of your methods regarding the spelling of the word "Validate".
This change would allow authentication workflows that occur over the CAS 3.0 protocol to return the custom attributes specified in the CAS configuration to the client by default. As in many cases additional custom mapped attributes are stored there, like first name, last name, phone numbers, etc.
In the event that sensitive information is being sent over this context, returning the attributes can be disabled.
Please let me know if you have an issues with this implementation or would like to discuss further. There may be arguments to having this feature default to false instead of true.
Thank you!