|As a user that is defined as an admin by the corresponding role, you can hit the settings button by clicking on your user profile name on the top right corner.
Within the settings panel, you can define several settings: Server, Password, License, Authentication, Messages, Log and Server Environment.
In addition to the settings, you can also send an error report, change the language (German or English) or the design (light or dark) to set or unset the dark mode. You can also view the version info of your Simplifier instance or log out.
The Server Settings are diveded into four parts: settings contolling the authentication token, settings controlling the email server connection (SMTP settings), settings controlling the artifakt graph and the configuration of the cluster mode.
|Activate expiry of the token in case of inactivity||
Enables all tokens to expire after the time defined below in case of inactivity. This means, a user gets automatically logged out after the time specified in “Idle time until the token is invalidated” of inactivity.
|Idle time until the token is invalidated||
The duration in seconds that a token remains valid during inactivity. This has only an effect if “Activate expiry of the token in case of inactivity” is enabled.
|Activate maximum token validity||
Enables all tokens to expire after the time defined below. This means, a user automatically gets logged out after the time defined in “Maximum token validity”. This enforces the logout, regardless wether or not there was any activity of the user
|Maximum token validity||
The maximum duration in seconds that a token is valid. This has only an effect if “Activate maximum token validity” is activated.
Define the email settings within the SMTP Settings.
|Send E-Mails||Enable or disable the sending of E-Mails generally|
|SMTP Host||Domain Name or IP Address of the E-Mail Server|
|SMTP Port||Specify the port of the outgoing mail server, e.g. 587|
|Authentication required||If activated, a user/password authentication from the outgoing mail server is required|
|Encrypted with TLS||If activated, the transmission is encrypted by TLS|
|Sender E-Mail||Enter the sender’s email address, e.g. email@example.com|
|Sender||Specify the name of the sender to be displayed|
|Username||Username to authenticate at the SMTP Server. Often it is the same as the E-Mail Adress|
|Change Password||Enable this, if you want to change the currently set password|
|Password and Confirm Password||Set a secure password|
Artifact Graph Settings
Please change the settings regarding the Artifact Graph only if the Simplifier support asks you to do so and only change the values to the ones given you from the support team.
Otherwise, please leave all values to their default values. Per default, all switches as disabled and all text input fields are empty.
The Cluster Mode is explained here: Cluster Mode
The security settings are diveded in two parts, the password settings and the behaviour settings.
The Password settings specify the password policy for the users.
|Minlength||Minlength defines the minimum length of a password. Set a high number for added security|
|Count lowercase characters||Defines the minimum count of lowercase characters in passwords, e.g. setting it to 4 means that a password has to be “abcdEFG” (at least four lowercase characters)|
|Count uppercase characters||Defines the minimum count of uppercase characters in passwords, e.g. setting it to 4 means that a password has to be “ABCDefg” (at least four uppercase characters)|
|Count numbers||Defines the minimum count of numbers in passwords, e.g. setting it to 4 means that a password has to be “1234abc” (at least four numerical characters)|
|Force symbols||This forces the user to use at least one symbol such as $%&#|
|Prohibit parts of the username||This option prohibits users from using their username or parts of it for their password, e.g. the user ‘John’ cannot use a password like ‘John123’|
Behaviour settings control different security relevant parts
|Block user after specified number of failed attempts||Specify a limit for failing logins to prevent Brute Force Attacks. If the user exceeds the limit he will be blocked. To unlock the user, the admin has to do this via the user management or the user can reset his password to unlock himself|
|Demand captcha after specified number of failed attempts||This option demands a captcha after a specified number of failed attempts|
|Activate deprecated Connector API||Activates an deprecated API version. Only activate this if you are told to do so by the Simplifier Support.|
|Enhanced Business Object Security||Activate permission check for executing Business Objects|
|Enhanced Template Security||Activate persmission check for rendering Templates|
|Activate Enhanced Connector Execution Security||Activate enhanced security settings for the execution of Connector calls via the public client route (…/client/2.0/Connector/). If you enable the option, an API key is generated that must be transmitted as header parameter “SimplifierApiKey” for all calls via this route in the future.
Note: This does not affect the execution of connectors from within Simplifier Apps.
|The License settings offer information about the current license you use. If your license expires, you can update it here. Simply copy and paste the license key in the corresponding field.|
Take a look at Authentication Settings and the following subpages.
|The Message settings allow you to store system messages, which are transmitted to all logged-in users, e.g. if you want to inform them about maintenance work.
With corresponding rights (assigned role “System Messages”), you can add a validity date. The messages can be written in HTML. As soon as a message is stored, it is pushed to all user. A user who logs in later receive the message as well. The message is displayed as an overlay and must be closed manually.
|Within the settings, you find the settings for the logs. You can define per categories, which log level will write a log in the logs & Monitoring.
Choose from the following categories:
Use the Log Archive Settings to specify the time period for archiving the logs. It runs every day at 3 a. m. when it’s activated.
Take a look at Server Environment.