Configuration parameter | Meaning |
---|---|
QER\Person\UseCentralPassword |
This configuration parameter specifies whether the employee's central password is used in the user accounts. The employee’s central password is automatically mapped to the employee’s user account in all permitted target systems. This excludes privileged user accounts, which are not updated. |
QER\Person\UseCentralPassword\PermanentStore |
This configuration parameter controls the storage period for central passwords. If the parameter is set, the employee’s central password is permanently stored. If the parameter is not set, the central password is only used for publishing to existing target system specific user accounts and is subsequently deleted from the One Identity Manager database. |
TargetSystem\GoogleApps\Accounts\ InitialRandomPassword |
This configuration parameter specifies whether a random generated password is issued when a new user account is added. The password must contain at least those character sets that are defined in the password policy. |
You have the following possible options for issuing an initial password for a new user account.
If the configuration parameter "QER\Person\UseCentralPassword" is set, the employee's central password is automatically mapped to an employee's user account in each of the target systems. This excludes privileged user accounts, which are not updated.
The password policy "Employee central password policy" is used to format the central password.
|
IMPORTANT: Ensure that the password policy "Employee central password policy" does not violate the target system specific password requirements. |
Assign a randomly generated initial password to enter when you create user accounts.
Configuration parameter | Meaning |
---|---|
TargetSystem\GoogleApps\DefaultAddress | The configuration parameter contains the recipient's default email address for sending notifications about actions in the target system. |
TargetSystem\GoogleApps\Accounts |
This configuration parameter specifies to which employee the email with the random generated password should be sent (manager cost center/department/location/business role, employee’s manager or XUserInserted). If no recipient can be found, the password is sent to the address stored in the configuration parameter "TargetSystem\GoogleApps\DefaultAddress". |
TargetSystem\GoogleApps\Accounts |
This configuration parameter contains the name of the mail template sent to inform users about their initial login data (name of the user account). Use the mail template "Employee - new account created". |
TargetSystem\GoogleApps\Accounts |
This configuration parameter contains the name of the mail template sent to inform users about their initial login data (initial password). Use the mail template "Employee - initial password for new user account". |
You can configure the login information for new user accounts to be sent by email to a specified person. In this case, two messages are sent with the user name and the initial password. Mail templates are used to generate the messages. The mail text in a mail template is defined in several languages, which means the recipient’s language can be taken into account when the email is generated. Mail templates are supplied in the default installation with which you can configure the notification procedure.
To use email notifications about login data
When a randomly generated password is issued for the new user account, the initial login data for a user account is sent by email to a previously specified person.
To send initial login data by email
By default, the message sent uses the mail template "Employee - new account created". The message contains the name of the user account.
By default, the message sent uses the mail template "Employee - initial password for new user account". The message contains the initial password for the user account.
|
TIP: Change the value of the configuration parameter in order to use custom mail templates for these mails. |
In order to handle G Suite specific processes in One Identity Manager, the synchronization server and its server functionality must be declared. You have several options for defining a server's functionality:
Create an entry for the Job serverServer with the One Identity Manager Service installed. in the category Base Data | Installation | Job server in the Designer. For detailed information, see the One Identity Manager Configuration Guide.
Use this task if the Job server has already been declared in One Identity Manager and you want to configure special functions for the Job server.
|
NOTE: One Identity Manager Service must be installed, configured and started in order for a server to execute its function in the One Identity Manager network. Proceed as follows in the One Identity Manager Installation Guide. |
To edit a Job server and its functions
|
NOTE: All editing options are available to you in the Designer, in the category Base Data | Installation | Job server |
Property |
Meaning | ||
---|---|---|---|
Server | Job server name. | ||
Full server name | Full server name in accordance with DNS syntax.
Example: <Name of servers>.<Fully qualified domain name> | ||
Target System |
Computer account target system. | ||
Language culture | Language of the server. | ||
Server is cluster | Specifies whether the server maps a cluster. | ||
Server belongs to cluster | Cluster to which the server belongs.
| ||
IP address (IPv6) | Internet protocol version 6 (IPv6) server address. | ||
IP address (IPv4) | Internet protocol version 4 (IPv4) server address. | ||
Copy process (source server) | Permitted copying methods that can be used when this server is the source of a copy action. Only the methods "Robocopy" and "Rsync" are currently supported.
If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication then takes place between servers with a Windows operating system using "Robocopy" and between servers with the Linux operating system using "rsync". If the operating systems of the source and destination servers differ, it is important that the right copy method is applied for successful replication. A copy method is chosen that supports both servers. | ||
Copy process (target server) | Permitted copying methods that can be used when this server is the destination of a copy action. | ||
Coding | Character set coding that is used to write files to the server. | ||
Parent Job server | Name of the parent Job server. | ||
Executing server | Name of the executing server. The name of the server that exists physically and where the processes are handled.
This input is evaluated when One Identity Manager Service is automatically updated. If the server is handling several queues the process steps are not supplied until all the queues that are being processed on the same server have completed their automatic update. | ||
Queue | Name of the queue to handle the process steps. Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the job queue using exactly this queue name. The queue identifier is entered in the One Identity Manager Service configuration file. | ||
Server operating system | Operating system of the server. This input is required to resolve the path name for replicating software profiles. Permitted values are "Win32", "Windows", "Linux" and "Unix". If the input is empty, "Win32" is assumed. | ||
Service account data | One Identity Manager Service user account information. In order to replicate between non-trusted systems (non-trusted domains, Linux server) the One Identity Manager Service user information has to be declared for the servers in the database. This means that the service account, the service account domain and the service account password have to be entered for the server. | ||
One Identity Manager Service installed | Specifies whether a One Identity Manager Service is installed on this server. This option is enabled by the procedure QBM_PJobQueueLoad the moment the queue is called for the first time.
The option is not automatically removed. If necessary, you can reset this option manually for servers whose queue is no longer enabled. | ||
Stop One Identity Manager Service | Specifies whether the One Identity Manager Service has stopped. If this option is set for the Job server, the One Identity Manager Service does not process any more tasks.
You can make the service start and stop with the appropriate administrative permissions in program "Job Queue Info". | ||
No automatic software update | Specifies whether to exclude the server from automatic software updating.
| ||
Software update running | Specifies whether a software update is currently being executed. | ||
Server Function | Server functionality in One Identity Manager. One Identity Manager processes are handled depending on the server function. |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy