ching.html
>
> Cheers,
> D.
>
>
> From: Павел Антонов
> Reply: cas-user@apereo.org
> Date: October 19, 2018 at 4:00:32 AM
> To: cas-user@apereo.org
> Subject: Re: [cas-user] Rerequesting CAS attributes
>
> Ray, I need to apply new attributes (changed in
/integration/Attribute-Release-Caching.html
Cheers,
D.
From: Павел Антонов
Reply: cas-user@apereo.org
Date: October 19, 2018 at 4:00:32 AM
To: cas-user@apereo.org
Subject: Re: [cas-user] Rerequesting CAS attributes
Ray, I need to apply new attributes (changed in CAS) to already
Pavel,
I see. You are right that the attributes will be outdated.
I do not know if there is a way to refresh without login.
This sounds similar to a unix login session; if something like group membership
is changed, user will need to log in again to see the change.
Ray
On Fri, 2018-10-19 at 11:
Ray, I need to apply new attributes (changed in CAS) to already
authenticated user.
How can i do this without logoff/logon currently authenticated user?
Does your recommendation solve my problem? I think "Map attributes =
principal.getAttributes()" will return the outdated attributes obtained
durin
Pavel,
I suspect getting attributes for protocol 3 will be same as SAML 1.1.
AttributePrincipal principal = (AttributePrincipal)request.getUserPrincipal();
Map attributes = principal.getAttributes();
There should be no need to go back to CAS.
Ray
On Thu, 2018-10-18 at 05:31 -0700, Pavel Anton
Hi! I'm developing an API using the Spring Framework.
CAS server version 5.3.1, CAS protocol version 3 and CAS client included
with Spring Security are used for user authentication.
Based on this example
https://apereo.github.io/2018/02/20/cas-service-rbac-attributeresolution/ I
use CAS attribut
