[cas-dev] Mutable user Attributes

[dale77]

Hello,

we have written our own AttributeRepository implementing IPersonAttributeDao
that returns custom user attributes. This works well for transferring our
custom attributes through in the CAS validation response.

However, when the user's attributes change after they have logged in, we
would like subsequent validation requests for that user to return the
modified attributes. Our primary use case is where the user modifies his
"profile" attributes which we are sending to applications in the validation
response.

Currently what CAS does is call our attribute repository once when the user
authenticates, then store a copy of the attributes in a SimplePrincipal. It
is the "stale" copy of these attributes which is returned to users when they
validate an new service ticket. 

I'd appreciate any advice on how to proceed with a Principal implementation
which hits our AttributeRepository for each service ticket validation
request, rather than just once at authentication. We want the user
attributes returned to always be up to date with our back end attribute
store.

Thanks

Dale
-- 
View this message in context: http://www.nabble.com/Mutable-user-Attributes-tp15885364p15885364.html
Sent from the CAS Dev mailing list archive at Nabble.com.