The links above are valid for 3.4 too. The only changes are that RegisteredService class dont have logoutType, requiredHandler attributeFilter properties.
Old docs: https://wiki.jasig.org/pages/viewpage.action?pageId=6620057 So... filtering is available through cas management webapp or in if you are using an in-memory ServiceRegistryDao set in deployerConfigContext.xml file. Therefore setting the property allowedAttributes of your RegisteredService beans you only exposes that attributes to that service/app. El 19/06/2014 09:59, "Philippe Vandenhove" <[email protected]> escribió: > > Unfortunately we use the 3.4.7. Is there another way to apply a filter with this version ? > > We can't return all to all applications without a filter (security). > > Regards, > > > 2014-06-18 13:45 GMT+02:00 KaTeLmE <[email protected]>: > >> Then i suggest you to return all and organize your roles. >> >> In cas4 you can specify an attribute filter by service in your service repository bean so putting an prefix and aplying it will be successful >> >> In the other hand you always can declare in the cas management app your services and establish what attributes you want to return. >> >> I dont know but in that cases i thinh is better the UNICON json service repository implementation. >> >> Take a look... >> >> http://jasig.github.io/cas/4.0.0/installation/Service-Management.html >> >> http://jasig.github.io/cas/4.0.0/integration/Attribute-Release.html >> >> El 17/06/2014 15:53, "Philippe Vandenhove" <[email protected]> escribió: >> >>> No. >>> >>> I need to know when the user changed from app A to app B to refresh user roles. >>> >>> User roles are returned by cas in SAML to applications . >>> >>> Regards, >>> >>> >>> 2014-06-17 15:35 GMT+02:00 KaTeLmE <[email protected]>: >>>> >>>> Do you mean renew features to force authentication on app B? >>>> >>>> El 17/06/2014 11:00, "Philippe Vandenhove" < [email protected]> escribió: >>>>> >>>>> Hi, >>>>> >>>>> I'm wondering if is there a way to detect within cas that the user has changed of application (Step 6 in the scenario below). >>>>> >>>>> Scenario >>>>> ------------ >>>>> #1 User goes to application A >>>>> #2 Application A redirect to CAS >>>>> #3 User authenticates >>>>> #4 Redirection to application A >>>>> #5 User goes to application B >>>>> #6 Cas detects that the user changed of application >>>>> >>>>> Regards, >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>> >>>> -- >>>> 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 >>> >>> >>> -- >>> 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 >> >> -- >> 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 > > > > -- > 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 -- 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
