| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
tutorial:adm:notifications_standard [2019/07/29 12:04]
svandav |
tutorial:adm:notifications_standard [2019/08/07 19:05]
apeterova |
| </note> | </note> |
| |
| ^ Check ^ Topic ^ Channel ^ Note / usage ^ | ^ Check ^ Topic ^ Channel ^ Note / usage ^ |
| | CHECK | acc:newPassword | email | After creating a new account, IdM will send the generated password to the user, who is the owner of the account. This can be turned off by deactivating the ''provisioning-send-notification-processor'' processor | | | CHECK | acc:newPassword | email | After creating a new account, IdM will send the generated password to the user, who is the owner of the account. This can be turned off by deactivating the ''provisioning-send-notification-processor'' processor | |
| | | acc:provisioning | websocket | IdM displays information about the result of provisioning to a system (can be visible also after approving a role request) | | | | acc:provisioning | websocket | IdM displays information about the result of provisioning to a system (can be visible also after approving a role request) | |
| | | acc:provisioningBreakDisable | email | If a [[tutorial:adm:create_provisioning_break|provisioning brake]] is configured and starts braking, IdM will send an email to the configured recipients (usually admins) | | | | acc:provisioningBreakDisable | email | If a [[tutorial:adm:create_provisioning_break|provisioning brake]] is configured and starts braking, IdM will send an email to the configured recipients (usually admins) | |
| | | acc:provisioningBreakWarning | email | If a [[tutorial:adm:create_provisioning_break|provisioning brake]] is configured and the warning limit is reached, IdM will send an email to the configured recipients (usually admins) | | | | acc:provisioningBreakWarning | email | If a [[tutorial:adm:create_provisioning_break|provisioning brake]] is configured and the warning limit is reached, IdM will send an email to the configured recipients (usually admins) | |
| | | core:bulkActionEnd | email | IdM will notify the user, who started some [[devel:documentation:bulk_actions|bulk action]], about the result of the action | | | | core:bulkActionEnd | email | IdM will notify the user, who started some [[devel:documentation:bulk_actions|bulk action]], about the result of the action | |
| | CHECK | core:changeIdentityRole | email | After changing assigned roles of the user manually (after the role request is finished - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[tutorial:adm:role_change_notification_configuration|Read more]] | | | CHECK | core:changeIdentityRole | email | After changing assigned roles of the user manually (after the role request is finished - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[tutorial:adm:role_change_notification_configuration|Read more]] | |
| | CHECK | core:changeIdentityRoleImplementer | email | After changing assigned roles of the user manually (after the request is finished), IdM will send the information to the user, who requested the change. This can be turned off by the configuration property ''idm.sec.core.wf.notification.implementer.enabled=false''. [[tutorial:adm:role_change_notification_configuration|Read more]] | | | CHECK | core:changeIdentityRoleImplementer | email | After changing assigned roles of the user manually (after the request is finished), IdM will send the information to the user, who requested the change. This can be turned off by the configuration property ''idm.sec.core.wf.notification.implementer.enabled=false''. [[tutorial:adm:role_change_notification_configuration|Read more]] | |
| | CHECK | core:disapproveIdentityRole | email | Same as core:changeIdentityRole, only for disapproved requests | | | CHECK | core:disapproveIdentityRole | email | Same as core:changeIdentityRole, only for disapproved requests | |
| | CHECK | core:disapproveIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for disapproved requests | | | CHECK | core:disapproveIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for disapproved requests | |
| | | core:loginBlocked | email | If maximum login attempts is specified in the [[devel:documentation:password_policies|password policy]] and a user exceeds this limit, this notification is sent to the user. | | | | core:loginBlocked | email | If maximum login attempts is specified in the [[devel:documentation:password_policies|password policy]] and a user exceeds this limit, this notification is sent to the user. | |
| | CHECK | core:passwordChanged | email | Users are notified about every change of their passwords. This can be turned off by deactivating the ''identity-password-change-notification'' processor | | | CHECK | core:passwordChanged | email | Users are notified about every change of their passwords. This can be turned off by deactivating the ''identity-password-change-notification'' processor | |
| | CHECK | core:passwordSet | email | The standard HR process (the scheduled task HrEnableContractProcess) resets the password and sends it to the user, when the user is activated for the first time (his first contract starts). This can be turned off by deactivating the ''identity-set-password-processor'' processor | | | CHECK | core:passwordSet | email | The standard HR process (the scheduled task HrEnableContractProcess) resets the password and sends it to the user, when the user is activated for the first time (his first contract starts). This can be turned off by deactivating the ''identity-set-password-processor'' processor | |
| | | core:passwordExpirationWarning | email | If the maximum password age is configured in the [[devel:documentation:password_policies|password policy]] and the task PasswordExpirationWarningTaskExecutor is scheduled, IdM will send this notification to the users about near password expiration | | | | core:passwordExpirationWarning | email | If the maximum password age is configured in the [[devel:documentation:password_policies|password policy]] and the task PasswordExpirationWarningTaskExecutor is scheduled, IdM will send this notification to the users about near password expiration | |
| | | core:passwordExpired | email | If the maximum password age is configured in the [[devel:documentation:password_policies|password policy]] and the task PasswordExpiredTaskExecutor is scheduled, IdM will send this notification to the users about their expired password | | | | core:passwordExpired | email | If the maximum password age is configured in the [[devel:documentation:password_policies|password policy]] and the task PasswordExpiredTaskExecutor is scheduled, IdM will send this notification to the users about their expired password | |
| | CHECK | core:returnRequestIdentityRole | email | Same as core:changeIdentityRole, only for returned requests | | | CHECK | core:returnRequestIdentityRole | email | Same as core:changeIdentityRole, only for returned requests | |
| | CHECK | core:returnRequestIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for returned requests | | | CHECK | core:returnRequestIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for returned requests | |
| | CHECK | core:wfTaskAssigned | email | If an approval task is created for the user, the user will be notified about the task. This is must be enabled by configuration property ''idm.sec.core.wf.notification.send=true''. The notification contains URL to the task, so URL of the server (e.g. https://idm.domain.tld) must be set as first value in the configuration property ''idm.pub.security.allowed-origins''. | | | CHECK | core:wfTaskAssigned | email | If an approval task is created for the user, the user will be notified about the task. This is must be enabled by configuration property ''idm.sec.core.wf.notification.send=true''. The notification contains URL to the task, so URL of the server (e.g. https://idm.domain.tld) must be set as first value in the configuration property ''idm.pub.security.allowed-origins''. | |
| | CHECK | core:wfTaskCreated | email | If an approval task is created for the user, the user will be notified about the task. The configuration is same as for core:wfTaskAssigned. | | | CHECK | core:wfTaskCreated | email | If an approval task is created for the user, the user will be notified about the task. The configuration is same as for core:wfTaskAssigned. | |
| | | vs:vsRequestCreated | email | If a new request on a [[devel:documentation:modules_vs|virtual system]] is created, the implementer of the virtual system will be notified about the request | | | | vs:vsRequestCreated | email | If a new request on a [[devel:documentation:modules_vs|virtual system]] is created, the implementer of the virtual system will be notified about the request | |
| | | core:changeIdentityRole (**topic: core:roleRequestRealizedApplicant**) | email | After changing assigned roles of the user manually (after the role request is finished **on all systems** - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]] | | | | core:changeIdentityRole (**topic: core:roleRequestRealizedApplicant**) | email | After changing assigned roles of the user manually (after the role request is **finished on all systems** - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]]. It can be turned on by activating the topic. | |
| | | core:changeIdentityRoleImplementer (**topic: core:roleRequestRealizedImplementer**) | email | After changing assigned roles of the user manually (after the request is **finished on all systems**), IdM will send the information to the user, who requested the change. This can be turned off by the configuration property ''idm.sec.core.wf.notification.implementer.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]] | | | | core:changeIdentityRoleImplementer (**topic: core:roleRequestRealizedImplementer**) | email | After changing assigned roles of the user manually (after the request is **finished on all systems**), IdM will send the information to the user, who requested the change. This can be turned off by the configuration property ''idm.sec.core.wf.notification.implementer.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]]. It can be turned on by activating the topic. | |
| |
| |
| |
| A configuration property can be set in **Settings** -> **Configuration**. | A configuration property can be set in **Settings** -> **Configuration**. |
| | |
| | A topic can be (de)activated in **Notifications** -> **Configuration** -> magnifying glass -> **Inactive** . |
| </note> | </note> |