The default One Identity Manager installation is supplied in the English - United States [en-US] and German - Germany [de-DE] language. You can add other languages to the user interface and display text if required. In this instance, you must translate the text before One Identity Manager goes live. There is a Language Editor in the Designer to help you do this. A special control is provided in the One Identity Manager tools that aids multi-language input.
One Identity Manager default language
Maintenance of default data takes place in the default language. The default language for an installation of One Identity Manager is English - United States [en-US]. The default language is valid across the system. It is not recommended to change the default language during working hours.
In the ideal case, the One Identity Manager language matches the user’s administration tool login language. If these two settings are different, then the default language is used if no captions are found in the requested login language for a set of language-dependent data.
User login language
The language used in the user interface is the same as the language used when logging in to the administration tools. When you log in for the first time, the system language is used for displaying the user interface. Users can change their login language in the program settings in all administration tools. This sets the language globally for all the user’s tools. Therefore, the user does not have to set the login language in every tool separately. Changes to the login language take effect after the tool is restarted.
Any language for which the Select in front-end option is activated can be used as a login language.
Related topics
Any language for which the Select in front-end option is activated can be used as a login language.
To enable an additional login language
-
In the Designer, select the Base data > Localization > Languages category.
-
In the List Editor, select the language.
-
In the Properties view, set the Select in front-end property to True.
-
Save the changes.
-
Select the Database > Commit to database and click Save.
Related topics
There are different ways to inform users that their password is going to expire:
-
Users are alerted about their password expiring when they log in to One Identity Manager and can change their password if necessary.
-
For employee-based authentication modules, the system sends reminder notifications in relation to expiring passwords as of seven days in advance of the password expiry date.
-
You can adjust the time in days in the Common | Authentication | DialogUserPasswordReminder configuration parameter. Edit the configuration parameter in the Designer.
-
The notifications are triggered in accordance with the Reminder system user password expires schedule and use the Employee - system user password expires mail template. You can adjust the schedule and mail template in the Designer if required.
TIP: To prevent passwords expiring for service account, for example, you can set Password never expires (DialogUser.PasswordNeverExpires) in the Designer for the affected system users.
When a user logs in, a validity check is run. Use the settings to configure additional options.
-
The system runs additional validity checks to prevent users from working with established connections, if they were deactivated after they logged in. The check takes place with next action on the connection after a fixed interval of 20 minutes.
You can adjust the interval in the Common | Authentication | CheckInterval configuration parameter. In the Designer, edit the configuration parameter.
-
The number of session that a user can open within a short time is limited to 10 session a minute.
If this number is exceeded, the user is sent an error message.
You have logged in too often in the last minute. Please wait a moment before you log in again.
This check is done for each front-end if the login is local. If the login is on the application server, it is checked for each application server.
You can modify the number of sessions in the Common | Authentication | SessionsPerUserAndMinute configuration parameter. In the Designer, edit the configuration parameter.
-
Use the QBM | AppServer | SessionTimeout configuration parameter to add the timeout in hours, after which inactive application server sessions are closed. The default value is 24 hours. In the Designer, edit the configuration parameter.
