[ https://issues.apache.org/jira/browse/SYNCOPE-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-1721: -------------------------------------------- Description: Currently, the association between Client Application and Access Policy is 1-to-1; moreover, the only defined Access Policy is the one mapped to CAS' {{{}DefaultRegisteredServiceAccessStrategy{}}}. Improvements: # let Client Applications define one or more Access Policies # add mapping for more CAS classes as ** {{HttpRequestRegisteredServiceAccessStrategy}} ** {{RemoteEndpointServiceAccessStrategy}} ** {{TimeBasedRegisteredServiceAccessStrategy}} was: Currently, the association between Client Application and Access Policy is 1-to-1; moreover, the only defined Access Policy is the one mapped to CAS' {{DefaultRegisteredServiceAccessStrategy}}. Improvements: # let Client Applications defined one or more Access Policies # add mapping for more CAS classes as ** {{HttpRequestRegisteredServiceAccessStrategy}} ** {{RemoteEndpointServiceAccessStrategy}} ** {{TimeBasedRegisteredServiceAccessStrategy}} > Allow for multiple and diverse Access Policies > ---------------------------------------------- > > Key: SYNCOPE-1721 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1721 > Project: Syncope > Issue Type: Improvement > Components: console, documentation, wa > Reporter: Francesco Chicchiriccò > Priority: Major > Fix For: 3.0.1, 4.0.0 > > > Currently, the association between Client Application and Access Policy is > 1-to-1; moreover, the only defined Access Policy is the one mapped to CAS' > {{{}DefaultRegisteredServiceAccessStrategy{}}}. > Improvements: > # let Client Applications define one or more Access Policies > # add mapping for more CAS classes as > ** {{HttpRequestRegisteredServiceAccessStrategy}} > ** {{RemoteEndpointServiceAccessStrategy}} > ** {{TimeBasedRegisteredServiceAccessStrategy}} -- This message was sent by Atlassian Jira (v8.20.10#820010)