Communication events
Communication events are generated when user notification (communication) is required.
Examples:
- A user was not logged in for three months and has to be warned before admin disables his account.
- A user has lost his password. Admin initates a password reset, which automatically sends the new password via e-mail to the user.
Communication event types
| Communication event name | Description |
|---|---|
| CertificateExpirationWarning | The event is generated by the batch job UpdateCredentialStateJob when a certificate credential is close to its configured expiry date. |
| DeactivationWarning | This event is generated by UpdateUserStateJob. |
| NewPassword | This event is generated by a password credential creation when the password is automatically generated. |
| OTP initial | This event is generated by an OTP credential creation or by an OTP card export in the GUI. |
| OTP renewal | This event is generated by an OTP credential renewal or by an OTP card export in the GUI. |
| OTP reset | This event is generated by an OTP credential reset or by an OTP card export in the GUI. |
| OTPExpirationWarning | The event is generated by the batch job UpdateCredentialStateJob when an OTP card is close to its configured expiry date. |
| OTPLowOnChallengesWarning | This event is generated when an OTP card is almost empty. |
| PUK initial | This event is generated by a PUK credential creation. |
| PUK reset | This event is generated by a PUK credential reset. |
| ResetCode | This event is generated by a password or device password credential reset. |
| SelfadminMobileNotification | This event is generated at SelfAdmin GUI mobile change verification process, when the client policy parameters gui.selfadmin.mobile.change.allowed and gui.selfadmin.mobile.change.verify are set to true. |
| SelfadminTicketNotification | This event is generated at SelfAdmin GUI e-mail change verification process, when the client policy parameters gui.selfadmin.email.change.allowed and gui.selfadmin.email.change.verify are set to true. |
| TempStrongPassword | This event is generated by a temporary strong password credential creation or reset. |
| Ticket | This event is generated by a ticket credential creation or reset. |
| TicketExpirationWarning | The event is generated by the batch job UpdateCredentialStateJob when a ticket credential is close to its configured expiry date. |
| URLTicketNotification | This event is generated by a URL ticket credential creation. |
| userNotification1-userNotification9 | Spare communication event types, used by IdmUserNotify AuthState. |
| Vasco assignment | This event is generated by the Vasco Digipass token assignment. |
Synchronous event handling
Whenever a communication has to take effect immediatly (GUI-activated events that are not printed directly), the event is handled synchronously, that means without saving it to persistent queue.
Asynchronous event handling
Events which are generated via the web service interface (WS clients, AuthStates), via batch jobs, or events which go directly to the printing queue, are handled asynchronously. This happens with the help of a persistent queue with various handler jobs that are active in the background (see the chapter: Events and persistent queue)
Document outputs
There are three types of OpenOffice document outputs: direct printout, PDF file stream for download and PDF file stored in the file system. E-mail documents have only one type: send to the recipient. The type of communication is defined in the credential policy with the parameter "sendingMethod" (see the chapter: Facing of web GUI design).
The outputs are never cached, that means they are generated anew on every printing event, accessing the template and filling the placeholders and tables from the database.