The Random Password Generator job creates a random password for each object defined in the job’s scope. The password is generated by NMAS to match a Password Policy object that the job references. Generally, each driver requires a password policy designed specifically for the connected system. If you don’t have a password policy to use, you need to create one before continuing with the job configuration. The job submits the generated passwords one at a time to the driver’s Subscriber channel. The Subscriber channel policies must take action on the passwords.
Make sure you’ve already added the job to the driver. If you haven’t, see Section 2.0, Adding a Predefined Job.
On the General tab in OpenText Identity Console (under Advanced > Jobs), configure the following options:
Enable job: Leave this option selected unless you don’t want the job to run.
Delete the job after the first run: Select this option if you want the job to run one time only and then be deleted.
Select the server(s) this job should run on: Select the servers where you want the job to run. Multiple servers are available only if the driver is running on multiple servers.
Email server: To monitor the job, you (or others) can receive email notifications whenever certain results occur for the job. You configure email notification on the Results tab. However, to enable this email notification to work, you must first specify the email server that will be used to send the notifications. Click the search button to locate and select the Default Notification Collection object or any other notfTemplateCollection object that defines an SMTP mail server. To send notifications, the job reads the target mail server and authentication credentials (except the password, which is specified in the Email server password field) from the selected Default Notification Collection object.
Email server password: Set the password for your email server account.
NOTE:If you do not specify a password, one of the following conditions will apply depending on the authentication method used by the mail server:
For basic authentication, the job reads the email server password from named passwords using the direxml.engine.smtp key, which is stored at the active driverset level.
For modern authentication, the client secret is used instead of email server password. In this case, the job reads the client secret from named passwords using the dirxml.engine.smtp.clientsecret key, which is also stored in the active driverset level.
Display name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
On the Schedule tab, you can select one of the following options:
Toggle to schedule job: Runs the job on a daily, weekly, monthly, or yearly schedule. You can also specify a custom schedule; use the crontab standard when specifying a custom schedule.
Toggle to run job manually: Runs the job only when you initiate it through the Start the selected job option (see Section 5.0, Starting a Job).
On the Scope tab, click the + Add an object to the job scope icon to add the objects for which you want to generate passwords.
On the Parameters tab, fill in the following fields:
Password Policy object used for password generation: Select the Password Policy object you want to use to generate the passwords. NMAS uses the password policy to generate the passwords. Generally, each driver requires a password policy designed specifically for the connected system. If you don’t have a password policy to use, click the Save icon to save the job’s current configuration, then create a password policy.
Generate a password for objects without a driver association: This is set to false by default. If you added objects to the Scope tab that are not associated with objects in the driver’s connected system, and you want to generate passwords for these objects, select true.
On the Results tab, define the actions you want performed based on the results for the job.
Each time the job runs, it generates intermediate results and a final result. For each result, you can specify the action you want performed when it occurs. For more information, see Understanding the Different States of a Job.
Click the No action link next to the result to display the Result Notification dialog box.
Select Audit result if you want to generate an event for Novell Audit or Novell Sentinel.
or
Select Send email, then fill in the recipient and e-mail template information.
Click OK to save your changes.
When you have finished configuring the job, click the Save icon to save your changes.
Select the job in the list (by selecting the check box next to the job name), then click the Get Status icon.
The Job Status dialog box displays any configuration errors. Because the job requires rights to the driver object and those rights have not yet been granted, you see an Insufficient rights to driver object error.
Click Grant rights, then click OK to confirm the action.
If other errors are displayed, resolve the errors. Otherwise, click OK to close the Job Status dialog box.