Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
devel:documentation:application_configuration:dev:backend [2021/07/14 08:38]
tomiskar [Identity]
devel:documentation:application_configuration:dev:backend [2021/10/19 19:05]
tomiskar [Authentication]
Line 123: Line 123:
 # you can use FE configuration https://wiki.czechidm.com/devel/documentation/application_configuration/dev/frontend # you can use FE configuration https://wiki.czechidm.com/devel/documentation/application_configuration/dev/frontend
 idm.pub.app.show.identity.table.columns=username, lastName, firstName, externalCode, email, state, description idm.pub.app.show.identity.table.columns=username, lastName, firstName, externalCode, email, state, description
 +idm.pub.app.show.identityRole.table.columns=role, roleAttributes, environment, identityContract, contractPosition, validFrom, validTill, directRole, automaticRole, incompatibleRoles
 # If is true, then role-request description will be show on the detail. # If is true, then role-request description will be show on the detail.
 # Description will hidden if this property will be false and role request # Description will hidden if this property will be false and role request
Line 553: Line 554:
 # Creates default identity's contract with configured position name. # Creates default identity's contract with configured position name.
 idm.sec.core.identity.create.defaultContract.position=Default idm.sec.core.identity.create.defaultContract.position=Default
-# Creates default identity's contract with configured state.+# Creates default identity's contract with configured state. Valid contract will be crated by default, other possible values: 
 +# EXCLUDED - Excluded from evidence - remains valid, but roles assigned for this contract are not added for logged identity. 
 +# DISABLED - Invalid by user - not changed by dates.
 idm.sec.core.identity.create.defaultContract.state= idm.sec.core.identity.create.defaultContract.state=
 # Number of days related to current date - will be used for set contract valid till date (current date + expiration in days = valid till). # Number of days related to current date - will be used for set contract valid till date (current date + expiration in days = valid till).
Line 889: Line 892:
  
 === CAS authentication filter === === CAS authentication filter ===
-@since 10.9.0+@since 12.0.0
 [[..:..:security:dev:security#cas_authentication|CAS authentication]] can be configured with following properties: [[..:..:security:dev:security#cas_authentication|CAS authentication]] can be configured with following properties:
 <code properties> <code properties>
-# Enable authentication via CAS. If enabled, all properties below "Other properties" become mandatory and must be set for SSO authentication via CAS to work. Default: false +# Enable authentication via CAS. If enabled, "idm.sec.core.cas.url" become mandatory and must be set for SSO authentication via CAS to work. Default: false 
-idm.pub.core.cas.sso.enabled=true+idm.pub.core.cas.enabled=false
 # Other properties # Other properties
 # Base URL where CAS is accessible. Syntax of this field is https://hostname-of-CAS/URI. # Base URL where CAS is accessible. Syntax of this field is https://hostname-of-CAS/URI.
-idm.pub.core.cas.url= +idm.sec.core.cas.url
-# Suffix which is, in effect, appended to idm.pub.core.cas.url. Resulting URL is used for login operation in CAS. It must start with slash (eg. /login). +# IdM service name configured as service on CAS server.  
-idm.pub.core.cas.login-suffix=/login?service= +# When service is configured, then login and logout redirect urls, should be defined directly in CAS service configuration. 
-# Suffix which is appended to idm.pub.core.cas.url. Resulting URL is used for single sign-out operation. It must start with slash (eg. /logout). +# Default: service name for login / logout is created dynamically by BE server url (recommended). 
-idm.pub.core.cas.logout-suffix=/logout?service= +idm.sec.core.cas.service
-URL of CzechIdM. This URL is used for redirect back after logout and also for ticket validation. Syntax of this field is https://hostname-of-CzechIdM/URI+# Suffix which is, in effect, appended to idm.sec.core.cas.url. Resulting URL is used for login operation in CAS. It must start with slash (eg. /login). 
-idm.pub.core.cas.idm-url+idm.sec.core.cas.login-path=/login 
-# Header name in which CAS sends the ticket value.+# Suffix which is appended to idm.sec.core.cas.url. Resulting URL is used for single sign-out operation. It must start with slash (eg. /logout). 
 +idm.sec.core.cas.logout-path=/logout 
 +Ticket can be given as request parameter (recommended, configured by default)
 +idm.sec.core.cas.parameter-name=ticket 
 +# Header name in which CAS sends the ticket value. Ticket can be given as request header. Not configured by default.
 idm.sec.core.cas.header-name=referer idm.sec.core.cas.header-name=referer
-# Path to CzechIdM for the HTTP Referer header used by CAS while redirecting back to application. This value is concatenated with CAS ticket to form Referer header. Syntax of this field is https://hostname-of-CzechIdM/URI/?ticket=.+# Path to CzechIdM for the HTTP Referer header used by CAS while redirecting back to application. This value is concatenated with CAS ticket to form Referer header. Syntax of this field is https://hostname-of-CzechIdM/URI/?ticket=. Not configured by default.
 idm.sec.core.cas.header-prefix= idm.sec.core.cas.header-prefix=
 </code> </code>
Line 1074: Line 1081:
 # Show thread name configured by thread pools (task, event) in logs (generated name is shown otherwise) # Show thread name configured by thread pools (task, event) in logs (generated name is shown otherwise)
 # Two appenders 'console' and 'file' are provided by product. Same configuration is needed for your custom appenders (added in logback.xml). # Two appenders 'console' and 'file' are provided by product. Same configuration is needed for your custom appenders (added in logback.xml).
-logging.pattern.console=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{36}.%M : %msg%n +logging.pattern.console=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{60}.%M : %msg%n 
-logging.pattern.file=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{36}.%M : %msg%n+logging.pattern.file=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{60}.%M : %msg%n
 </code> </code>
  
  • by chalupat