That means: 1. CAS might have some attributes cached already as part of primary authn.
2. CAS starts to retrieve attributes during a particular validation event, based on caching rules and if/when configured. 3. When it does, in case there are collisions between what it already had and what it retrieved again, there might be a need to merge. You told it to never merge. Merging attribute repositories from person directory is separate from this. It’s safe to ignore this based on you description. You’ll need to make sure attributes are allowed for release for that client, and the client is hitting the /p3/serviceValidate endpoint. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Warren White Sent: Wednesday, June 22, 2016 12:28 PM To: CAS Community <[email protected] <mailto:[email protected]> > Subject: [cas-user] Attributes retrieved server side, but not available to client I am attempting to include Principal Attributes for the client after login in via CAS 4.2.2 Server cas.log: 2016-06-22 10:56:04,428 DEBUG [org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl] - Retrieved attributes='[NamedPersonImpl[name=xyz,attributes={USER_ROLE=[login, admin, student]}]]' for query='{username=[xyz]}', isFirstQuery=false, currentlyConsidering='org.jasig.services.persondir.support.jdbc.MultiRowJdbcPersonAttributeDao@62aac52b', resultAttributes='[NamedPersonImpl[name=xyz,attributes={displayName=[xyz], uid=[1198], mail=[[email protected]]}]]' 2016-06-22 10:56:04,428 DEBUG [org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl] - Aggregated search results '[NamedPersonImpl[name=xyz,attributes={displayName=[xyz], uid=[1198], mail=[[email protected]], USER_ROLE=[login, admin, student]}]]' for query='{username=[xyz]}' 2016-06-22 10:56:04,429 DEBUG [org.jasig.cas.authentication.principal.cache.AbstractPrincipalAttributesRepository] - Found [4] attributes for principal [xyz] from the attribute repository. 2016-06-22 10:56:04,429 DEBUG [org.jasig.cas.authentication.principal.cache.AbstractPrincipalAttributesRepository] - No merging strategy found, so attributes retrieved from the repository will be used instead. I have merged attributes from a SingleRowJdbcPersonAttributeDao and from a MultiRowJdbcPersonAttributeDao, both are working, as the Aggregated results show. The debug also shows Found 4 attributes found for principal. I am confused about the last debug statement "No merging strategy found....", but I am merging the attributes. And the client side, only the Principal attribute id is returned, no other attributes. How to access the Principal Attributes from client? -- 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] <mailto:[email protected]> . To post to this group, send email to [email protected] <mailto:[email protected]> . Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/197787c8-2e0c-4106-a11a-fe04acf4df3c%40apereo.org <https://groups.google.com/a/apereo.org/d/msgid/cas-user/197787c8-2e0c-4106-a11a-fe04acf4df3c%40apereo.org?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/a/apereo.org/d/optout. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/006c01d1ccd9%24757fe2e0%24607fa8a0%24%40unicon.net. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
