Apache Syncope Attribute Resolution
The following configuration describes how to fetch and retrieve attributes from Apache Syncope.
The following settings and properties are available from the CAS configuration catalog:
cas.authn.attribute-repository.syncope.basic-auth-password=
Specify the password for REST authentication.
|
cas.authn.attribute-repository.syncope.basic-auth-username=
Specify the username for REST authentication.
|
cas.authn.attribute-repository.syncope.domain=Master
Syncope domain used for authentication, etc. Multiple domains can be separated via comma. Each domain entry results in a separate authentication attempt and transaction by CAS.
|
cas.authn.attribute-repository.syncope.search-filter=
User FIQL filter to use for searching. Syntax is
|
cas.authn.attribute-repository.syncope.url=
Syncope instance URL primary used for REST.
|
cas.authn.attribute-repository.syncope.attribute-mappings=
Map of attributes that optionally may be used to control the names of the collected attributes from Syncope. If an attribute is provided by Syncope, it can be listed here as the key of the map with a value that should be the name of that attribute as collected and recorded by CAS. For example, the convention
|
cas.authn.attribute-repository.syncope.headers=
Headers, defined as a Map, to include in the request when making the REST call. Will overwrite any header that CAS is pre-defined to send and include in the request. Key in the map should be the header name and the value in the map should be the header value.
|
cas.authn.attribute-repository.syncope.id=
A value can be assigned to this field to uniquely identify this resolver.
|
cas.authn.attribute-repository.syncope.order=0
The order of this attribute repository in the chain of repositories. Can be used to explicitly position this source in chain and affects merging strategies.
|