Differences

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

--- devel:documentation:application_configuration:dev:backend [2019/06/11 06:57]
tomiskar [Configure environment properties]
+++ devel:documentation:application_configuration:dev:backend [2020/01/29 12:55]
tomiskar [Attachment storage]
@@ Line 91: / Line 91: @@
 # Show transaction identifiers (uuid) in frontend application
 idm.pub.app.show.transactionId=false
+# Show role environmnent in frontend application for roles (table, role detail, niceLabel, info components, role select)
+idm.pub.app.show.environment=true
 #
 # Private properties - used on backend only.
@@ Line 216: / Line 218: @@
 # older temporary files will be purged, default 14 days
 idm.sec.core.attachment.tempTtl=1209600000
-#
-# Max file size of uploaded file. Values can use the suffixed "MB" or "KB" to indicate a Megabyte or Kilobyte size.
-multipart.max-file-size=1Mb
 </code>
@@ Line 227: / Line 225: @@
 #
 # Max file size of uploaded file. Values can use the suffixed "MB" or "KB" to indicate a Megabyte or Kilobyte size.
-multipart.max-file-size=1Mb
+multipart.max-file-size=100Mb
 </code>
@@ Line 679: / Line 677: @@
 idm.sec.core.authentication-filter.core-sso-authentication-filter.forbidden-uids=
 </code>
+=== Remote user authentication filter ===
+Login into IdM by preset request remote user by servlet container can be configured with following properties:
+<code properties>
+# Allow remote user authentication
+idm.sec.core.authentication-filter.core-remote-user-authentication-filter.enabled=false
+# The suffixes to remove from the login - usually domains
+idm.sec.core.authentication-filter.core-remote-user-authentication-filter.uid-suffixes=
+# The uids that can't be authenticated by SSO
+idm.sec.core.authentication-filter.core-remote-user-authentication-filter.forbidden-uids=
+</code>
+This authentication filter reuses SSO authentication filter behavior above (''uid-suffixes'', ''forbidden-uids''), but application administrator can be logged by this filter (identity with ''APP_ADMIN'' authority).
 ==== Backup ====
-If you want to use redeploy and backup for example in agenda (notification template), you must define default backup folder see:
+If you want to use redeploy and backup for example in agenda (notification templates, scripts), you must define default backup folder.
+When redploy is used, then actual templates (or scripsts) are loaded from classpath by configuration (for templates or scripts) and deployed into application. Previous templates (or scripts) are backup too.
 <code properties>
 # configuration property for default backup
@@ Line 714: / Line 727: @@
 idm.sec.vs.role.default=<some-code-of-role>
 </code>
+==== Long polling ====
+<code properties>
+# Long polling
+idm.pub.app.long-polling.enabled=true
+</code>
+You can disable long polling for all types of entites with use value `false`.
 ==== Provisioning ====
@@ Line 818: / Line 840: @@
 Common configuration properties for all renderers:
   * ''enabled'' - on / off
+==== Logger ====
+In the application profile (''application.properties'') - overloadable via ''ConfigurationService''.
+Logger levels can be configured programmatically (override ''logback.xml'' file with default logger levels configuration).
+<code properties>
+idm.sec.core.logger.<packageName>=<level>
+</code>
+Where ''<packageName>'' is package name to set logger ''<level>''.
+Example:
+<code properties>
+idm.sec.core.logger.eu.bcvsolutions=DEBUG
+</code>