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/05/05 09:17]
tomiskar [Application/ Server] 		devel:documentation:application_configuration:dev:backend [2021/06/28 13:33]
127.0.0.1 external edit
Line 77: Line 77:
 # Show role baseCode in frontend application for roles (table, role detail, niceLabel, info components, role select). # Show role baseCode in frontend application for roles (table, role detail, niceLabel, info components, role select).
 idm.pub.app.show.role.baseCode=true idm.pub.app.show.role.baseCode=true
 +# Rendered column in role table agenda. Comma is used as separator. Order of rendered columns is preserved as configured.
 +# Available columns:
 +# - name - role name info card with link to detail
 +# - baseCode - role base code (without environment)
 +# - environment - role environment
 +# - disabled
 +# - description
 +idm.pub.app.show.role.table.columns=name, baseCode, environment, disabled, description
 +# Show role catalogue item code in role catalogue tree
 +idm.pub.app.show.roleCatalogue.tree.code=false
 # Number of items (pagination) in role catalogue tree in root level. Used on role select and agenda. # Number of items (pagination) in role catalogue tree in root level. Used on role select and agenda.
 idm.pub.app.show.roleCatalogue.tree.pagination.root.size=25 idm.pub.app.show.roleCatalogue.tree.pagination.root.size=25
Line 142: Line 152:
  
 Bulk action is available for logged user with required authorities and permissions: Bulk action is available for logged user with required authorities and permissions:
-  * ''CONFIGURATION\_UPDATE'' - configuration property contains instance for asynchronous processing will be changed => authority and ''UPDATE'' base permission for property ''idm.sec.core.event.asynchronous.instanceId'' is reguired.+  * ''CONFIGURATION\_UPDATE'' - configuration property contains instance for asynchronous processing will be changed => authority and ''UPDATE'' base permission for property ''idm.sec.core.event.asynchronous.instanceId'' is required.
   * ''SCHEDULER\_UPDATE'' - scheduled tasks and created (~ not processed) asynchronous long running tasks will be changed.   * ''SCHEDULER\_UPDATE'' - scheduled tasks and created (~ not processed) asynchronous long running tasks will be changed.
   * ''ENTITYEVENT\_UPDATE'' - created (~ not processed) asynchronous events will be changed.   * ''ENTITYEVENT\_UPDATE'' - created (~ not processed) asynchronous events will be changed.
Line 961: Line 971:
  
 ==== Provisioning global break ==== ==== Provisioning global break ====
-<note tip>For enable global provisioning break you must set configurations properties defined below, otherwise global provisioning break will not be active.</note>+<note tip>For enable global provisioning break you must set configurations properties defined below, otherwise global provisioning break will not be activated.</note>
  
 <code properties> <code properties>
Line 1072: Line 1082:
 idm.sec.core.logger.eu.bcvsolutions=DEBUG idm.sec.core.logger.eu.bcvsolutions=DEBUG
 </code> </code>
 +
 +==== Monitoring ====
 +
 +=== Monitoring evaluator ===
 +
 +In the application profile (''application.properties'') - overloadable via ''ConfigurationService''.
 +
 +<code properties>
 +# disable / enable monitoring evaluator
 +idm.sec.<module>.monitoring-evaluator.<name>.enabled=true
 +</code>
 +Where ''<module>'' is monitoring's module a ''<name>'' is monitoring's name.
 +
 +Common configuration properties for all monitorings:
 +  * ''enabled'' - true / false
  • by chalupat