Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun[TM] Identity Manager 8.0 Administration 

Chapter 5
Configuration & System Maintenance

This chapter provides information and procedures for using the Administrator Interface to set up and maintain Identity Manager objects and server processes. For more information about Identity Manager objects, see Identity Manager Objects of the Overview chapter.


Note

For information about configuring Identity Manager for a Service Provider implementation, see Chapter 17, "Service Provider Administration."


This chapter is organized in the following topics:


Configuring Identity Manager Policies

Read this section for information and procedures for configuring user policies.

What are Policies?

Identity Manager policies set limitations for Identity Manager users by establishing constraints for Identity Manager account ID, login, and password characteristics.


Note

Identity Manager also provides Audit policies that are specifically designed to audit user compliance. Audit policies are discussed in Chapter 13, "Identity Auditing: Basic Concepts."


Opening the Policies Page

You create and edit Identity Manager user policies from the Policies page.

To open the Policies page, follow these steps:

  1. Log in to the Administrator interface.
  2. Click the Security tab, then click the Policies subtab.
  3. The Policies page opens.

Policy Types

Using the Policies page you can edit existing policies and create new ones.

Policies are categorized as the following types:

Must Not Contain Attributes in Policies

You can change the allowed set of “must not contain” attributes in the UserUIConfig configuration object. Attributes are listed in UserUIConfig as follows:

Dictionary Policy

A dictionary policy enables Identity Manager to check passwords against a word database to ensure that they are protected from a simple dictionary attack. By using this policy with other policy settings to enforce the length and makeup of passwords, Identity Manager makes it difficult to use a dictionary to guess passwords that are generated or changed in the system.

The dictionary policy extends the password exclusion list that you can set up with the policy. (This list is implemented by the Must Not Contain Words option on the Administrator Interface password Edit Policy page.)

Configuring the Dictionary Policy

To set up the dictionary policy, you must:

To set up the dictionary policy, follow these steps:

  1. Open the Policies page ((more...) ).
  2. Click Configure Dictionary to display the Dictionary Configuration page.
  3. Select and enter database information:
    • Database Type — Select the database type (Oracle, DB2, SQLServer, or MySQL) that you will use to store the dictionary.
    • Host — Enter the name of the host where the database is running.
    • User — Enter the user name to use when connecting to the database.
    • Password — Enter the password to use when connecting to the database.
    • Port — Enter the port on which the database is listening.
    • Connection URL — Enter the URL to use when connecting. These template variables are available:
      • %h - host
      • %p - port
      • %d - database name
    • Driver Class — Enter the JDBC driver class to use while interacting with the database.
    • Database Name — Enter the name of the database where the dictionary will be loaded.
    • Dictionary Filename — Enter the name of the file to use when loading the dictionary.
  4. Click Test to test the database connection.
  5. If the connection test is successful, click Load Words to load the dictionary. The load task may take a few minutes to complete.
  6. Click Test to ensure that the dictionary was loaded correctly.

Implementing the Dictionary Policy

To implement the dictionary policy, follow these steps:

  1. Open the Policies page ((more...) ).
  2. Click the Password Policy link to edit the password policy.
  3. On the Edit Policy page, select the Check passwords against dictionary words option.
  4. Click Save to save your changes.

Once implemented, all changed and generated passwords will be checked against the dictionary.


Customizing Email Templates

Identity Manager uses email templates to deliver information and requests for action to users and approvers. The system includes templates for:

Editing an Email Template

You can customize email templates to provide specific directions to the recipient, telling him how to accomplish a task or how to see results. For example, you might want to customize the Account Creation Approval template to direct an approver to an account approval page by adding the following message:

Please go to http://host.example.com:8080/idm/approval/approval.jsp to approve account creation for $(fullname).

To customize an email template, use the following procedure using the Account Creation Approval template as an example:

  1. In the Administrator interface, click the Configure tab, then click the Email Templates subtab.
  2. The Email Templates page opens.

  3. Click to select the Account Creation Approval template.
  4. Figure 5-3  Editing an Email Template
    Use the Edit Email Templates page to customize details for where, and to whom, email is sent when an action occurs.

  5. Enter details for the template:
    • In the SMTP Host field, enter the SMTP server name so that email notification can be sent.
    • In the From field, customize the originating email address.
    • In the To and Cc fields, enter one or more email addresses or Identity Manager accounts that will be the recipients of the email notification.
    • In the Email Body field, customize the content to provide a pointer to your Identity Manager location.
  6. Click Save.

You can also modify email templates by using the Identity Manager IDE. For information on the IDE, see Identity Manager IDE.

HTML and Links in Email Templates

You can insert HTML-formatted content into an email template to display in the body of an email message. Content can include text, graphics, and Web links to information. To enable HTML-formatted content, select the HTML Enabled option.

Allowable Variables in the Email Body

You can also include references to variables in the email template body, in the form $(Name); for example: Your password $(password) has been recovered.

Allowable variables for each template are defined in the following table.

.

Table 5-1  Email Template Variables

Template

Allowable Variables

Password Reset

$(password) – newly generated password

Update Approval

$(fullname) – user’s full name

$(role) – user’s role

Update Notification

$(fullname) – user’s full name

$(role) – user’s role

Report

$(report) – generated report

$(id) – encoded ID of the task instance

$(timestamp) – time when email was sent

Request Resource

$(fullname) – user’s full name

$(resource) – resource type

Risk Analysis

$(report) – risk analysis report

Temporary Password Reset

$(password) – newly generated password

$(expiry) – password expiration date


Configuring Audit Groups and Audit Events

Setting up audit configuration groups allows you to record and report on system events you select.

The Audit Configuration Page

Use the Audit Configuration page to set up audit groups. Setting up audit groups will enable you to run AuditLog reports later.

Opening the Audit Configuration Page

To open the Audit Configuration page, follow these steps:

  1. Open the Administrator interface.
  2. Click the Configure tab, then click the Audit subtab.
  3. The Audit Configuration page opens.

Configuring Audit Groups

Configuring audit groups and events requires the Configure Audit administrative capability.

If it is not already open, open the Audit Configuration page. (See steps, above.)

The Audit Configuration page shows the list of audit groups, each of which may contain one or more events. For each group, you can record successful events, failed events, or both.

Click an audit group in the list to display the Edit Audit Configuration Group page. This page lets you select the types of audit events to be recorded as part of an audit configuration group in the system audit log.

Check that the Enable auditing check box is selected. Clear the check box to disable the auditing system.


Note

For more information about audit groups, see Audit Configuration in the Audit Logging chapter.


Editing Events in the Audit Configuration Group

To edit events in the group, you can add or delete actions for an object type. To do this, move items in the Actions column from the Available to the Selected area for that object type, and then click OK.

Adding Events to the Audit Configuration Group

To add an event to the group, click New. Identity Manager adds an event at the bottom of the page. Select an object type from the list in the Object Type column, and then move one or more items in the Actions column from the Available area to the Selected area for the new object type. Click OK to add the event to the group.


Remedy Integration

You can integrate Identity Manager with a Remedy server, enabling it to send Remedy tickets according to a specified template.

Set up Remedy integration in two areas of the Administrator interface:

Creation of Remedy tickets is configured through Identity Manager workflow. Depending on your preferences, a call can be made at an appropriate time that uses the defined template to open a Remedy ticket. For more information about configuring workflows, see Identity Manager Workflows, Forms, and Views.


Configuring Identity Manager Server Settings

You can edit server-specific settings so that Identity Manager servers run only specific tasks.

To configure server-specific settings, follow these steps:

  1. In the Administrator interface, click Configure in the main menu, then click Servers.
  2. The Configure Servers page opens.

  3. Click a server in the list on the Configure Servers page to edit settings for an individual server.
  4. Identity Manager displays the Edit Server Settings page, where you can edit reconciler, scheduler, JMX and other settings.

Reconciler Settings

The reconciler is the Identity Manager component that performs reconciliation. To learn about reconciliation, see Reconciliation.

To configure reconciler settings, follow the steps under Configuring Identity Manager Server Settings. Select the Reconciler tab.

By default, reconciler settings display on the Edit Server Settings page. You can accept the default values or de-select the Use default option to specify custom values.


Note

To change the default reconciler settings used by Identity Manager servers, see Editing Default Server Settings.


Configure the reconciler using the following settings:

For information about tuning and troubleshooting the reconciler, see Identity Manager Tuning, Troubleshooting, and Error Messages.

Viewing Reconciler Status

To view reconciler status information, open the Reconciler Status debug page.


Note

You must have the Debug capability to view /idm/debug/ pages. For information about capabilities, see Assigning Capabilities.


To open the Reconciler Status debug page, type this URL into your browser:

http://<AppServerHost>:<Port>/idm/debug/Show_Reconciler.jsp

where AppServerHost is a host that has the reconciler enabled.

Refresh the Reconciler Status page to view updated reconciler status information. For additional information about this page, click Help.

Scheduler Settings

The scheduler component controls task scheduling in Identity Manager.

To configure scheduler settings on a particular server, follow the steps under Configuring Identity Manager Server Settings. Select the Scheduler tab.

You can accept the default values or de-select the Use default option to specify custom values.

Click Save to save changes to the server settings.

To change the default scheduler settings for Identity Manager servers, see Editing Default Server Settings.

For information about tuning and troubleshooting the scheduler, see Identity Manager Tuning, Troubleshooting, and Error Messages.

Email Template Server Settings

To configure SMTP server settings, follow the steps under Configuring Identity Manager Server Settings. Select the Email Template tab.

Specify the default email server by clearing the Use Default selection and entering the mail server to use, if other than the default. The text you enter is used to replace the smtpHost variable in Email Templates.

Simple Mail Transfer Protocol (SMTP) is the standard for email transmissions across the Internet.

To change the default SMTP settings for Identity Manager servers, see Editing Default Server Settings.

JMX

Java Management Extensions (JMX) is a Java technology that allows for managing and/or monitoring applications, system objects, devices, and service oriented networks. The managed/monitored entity is represented by objects called MBeans (for Managed Bean).

This section describes how to configure JMX on an Identity Manager server so that a JMX client can monitor the system for changes. (Identity Manager can also be configured to make audit events available via JMX. For information, see (more...) .)

Configure JMX Polling Settings

To configure JMX polling settings on an individual server, follow these steps:

  1. Follow the steps under Configuring Identity Manager Server Settings. Select the JMX tab.
  2. Enable JMX cluster polling and configure the interval for the polling threads by using the following options:
    • Enable JMX — Use this option to enable or disable the polling thread for the JMX Cluster MBean. To enable JMX, clear the default selection (Use Default (false)). Because of the use of system resources for polling cycles, enable this option only if you plan to use JMX.
    • Polling Interval (ms) — Use this option to change the default interval at which the server will poll the repository for changes, when JMX is enabled. Specify the interval in milliseconds.

      The default polling interval is set to 60000 milliseconds. To change it, clear the check box for this option and enter the new value in the entry field provided.

  3. Click Save to save changes to the server settings.

    Note

    To change the default JMX polling settings for Identity Manager servers, see Editing Default Server Settings.


Viewing JMX Data

Use a JMX client to view data gathered by JMX. JConsole, which is included in the JDK 1.5, is one such client.

Using JConsole Locally

To use JConsole on the same machine your server is running on, set the following property:

JConsole will connect using the correct PID.

Using JConsole Remotely

To use JConsole remotely, set the following properties:

Other settings may also be necessary depending on your environment. Refer to the JConsole documentation for more information.


Note

JMX data can also be viewed by going to the Identity Manager debug page ((more...) ) and clicking the Show MBean Info button.


For more information on JMX, visit this website:

http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/docs.jsp

Editing Default Server Settings

The Default Server Settings feature lets you set the default settings for all Identity Manager servers. The servers inherit these settings unless you select differently in the individual server settings pages.

To edit the default server settings, follow these steps:

  1. In the Administrator interface, click Configure > Servers.
  2. The Configure Servers page opens.

  3. Click Edit Default Server Settings.
  4. The Edit Default Server Settings page opens.

The Edit Default Server Settings page displays the same options as the individual server settings pages. For help, refer to the documentation for the individual server settings pages.

Changes you make to each default server setting is propagated to the corresponding individual server setting, unless you have de-selected the Use default option for that setting.

Click Save to save changes to the server settings.


Configuring the End-User Interface

Administrators can configure certain aspects of the end-user interface by modifying a form in the Administrator interface.

To set options for displaying information in the end-user interface, follow these steps:

  1. In the Administrator interface, click Configure in the main menu.
  2. Click User Interface in the secondary menu.
  3. The User Interface page opens.

  4. Complete and save the End User Dashboard portion of the form. Click Help if you need help with the form.
  5. For information on completing the Anonymous Enrollment portion of the form, see Anonymous Enrollment.

Enabling Process Diagrams in the End-User Interface

Process diagrams depict the workflow that Identity Manager follows when end-users launch a request or update their profile. When enabled, process diagrams display on the results page after the end-user submits a form.

Process diagrams must be enabled in the Administrator interface before they can be enabled in the end-user interface. See Enabling Process Diagrams for more information.

To enable process diagrams in the end-user interface, follow these steps:

  1. Open the User Interface configuration page by following the steps in Configuring the End-User Interface.
  2. Select the Enable End-User Process Diagrams option, which is located in the Result Pages section of the form.
  3. If the Enable End-User Process Diagrams option is not available, then you must first enable process diagrams in the Administrator interface. See Enabling Process Diagrams.

  4. Click Save.


Registering Identity Manager

Administrators are encouraged to register their installation of Identity Manager.

To register, you will need a Sun Online Account and password. If you do not have a Sun Online Account, you can register for one by completing the form at this address:

https://reg.sun.com/register

Identity Manager can be registered from the console or by using the Administrator interface.

Registering from the console allows you to also create a local service tag, which can be used with Sun Service Tag software to track your inventory of Sun systems, software, and services. The service tags client package should be installed before you create a local service tag. This package can be downloaded by clicking the Download Service Tags button at the following address:

http://inventory.sun.com/inventory

In order to register Identity Manager, you should be logged on with an administrator account that allows you to configure Identity Manager objects. This account should have the Product Registration capability. For information about capabilities, see Assigning Capabilities.


Note

Java on your Identity Manager application server(s) must be properly configured for SSL in order for the product registration feature to work. All JARs referenced in your java.security file (or equivalent) need to be present.


Registering Identity Manager from the Console

To create a local service tag, or register Identity Manager over the Internet with Sun, follow these steps:

  1. On Windows, start the Identity Manager console (command-line) interface by typing the following at a command line:
  2. %WSHOME%\bin\lh

    On Unix, start the Identity Manager console (command-line) interface by typing the following at a command line:

  1. To create a local service tag, use the following command:
  2. register -local

    To register Identity Manger over the Internet with Sun, use the following command:

    register -remote -u <userid> -p <password> -userSOA <soaUserid>
    -passSOA <soaPassword> -proxy <proxyHost> -port <proxyPortNumber>

    where:

    • userid is the Identity Manager userID of the Identity Manager administrator who is authorized to do the registration
    • password is the Identity Manager password of the Identity Manager administrator who is authorized to do the registration
    • soaUserid is the user ID of the Sun Online Account that will be used for registration.
    • soaPassword is the password of the Sun Online Account that will be used for registration.
    • proxyHost is the network proxy to use for access to the Sun online registration service. Only required if your network is configured to use a proxy to reach external Internet addresses.
    • proxyPortNumber is the port on the network proxy to use for access to the Sun online registration service. Only required if your network is configured to use a proxy to reach external Internet addresses

The register Command

Usage

register -local

register -remote [-u <userid> [-p <password>]] [-prompt] -userSOA <userid> -passSOA <password> [-proxy <proxyHost> [-port <proxyPortNumber>]] register [-help | -?]

Options

Use these options with the register command.:

Table 0-1  Syslog Command Options

Option

Description

-local

Create a service tag on this host.

-remote

Register this installation of Identity Manager over the network directly with Sun.

-u <userid>

The Identity Manager user ID of the Identity Manager administrator who is authorized to do the registration.

-p <password>

The Identity Manager password of the Identity Manager administrator who is authorized to do the registration.

-prompt

Interactively prompt for the password if missing.

-userSOA <userid>

The user ID of the Sun Online Account that will be used for registration.
Required if registering with the -remote option.

-passSOA <password>

The password of the Sun Online Account that will be used for registration.
Required if registering with the -remote option.

-proxy <proxyHost>

The network proxy to use for access to the Sun online registration service. Required if registering with the -remote option and your network is configured to use a proxy to reach external Internet addresses.

-port <proxyPortNumber>

The port on the network proxy to use for access to the Sun online registration service. Required if registering with the -remote option and your network is configured to use a proxy to reach external Internet addresses.

-help | -?

Print help for this command to the console.

Registering Identity Manager from the Administrator Interface

If you do not need to create a local service tag, register Identity Manager from the Administrator interface.

To register Identity Manager from the Administrator interface, follow these steps:

  1. In the Administrator interface, click Configure.
  2. In the secondary menu, click Product Registration.
  3. The Product Registration page opens.

  4. Complete the form and click Register Now. Click the i-Helps for information about individual form fields.

    Note

    If your application server is not configured to allow outgoing SSL connections, you may receive the following error message:

    Failed to register on Sun Connection server due to invalid Sun Online Account user/password.

    To resolve this issue, add the appropriate trusted root certificate(s) to your application server's keystore. Consult your application server's documentation for details.



    Note

    If old versions of xml-apis.jar and xercesImpl.jar are present in your application server's classpath, you may receive the following error message:

    java.lang.NoSuchMethodError:org.w3c.dom.Node.getTextContent() Ljava/lang/String;

    To resolve this problem, modify the classpath so that only the most recent versions of xml-apis.jar and xercesImpl.jar are present.



Editing Identity Manager Configuration Objects

In the course of administering Identity Manager, you will occasionally be called upon to edit the Identity Manager system configuration object (also referred to as the System Configuration File), or other similar objects.

To edit objects using the Administrator interface, follow these steps:

  1. Open the Identity Manager Debug Page by typing the following URL into your browser:
  2. http://<AppServerHost>:<Port>/idm/debug/session.jsp

    The System Settings page opens.


    Note

    You must have the Debug capability to view /idm/debug/ pages.


  3. Find the List Objects button, then select Configuration from the adjacent Type drop-down list.
  4. Click the List Objects button.

    The “List Objects of type: Configuration” page opens.

  5. In the list of objects, find the object you need, then click edit. For example, to edit the system configuration object, find System Configuration, then click edit.
  6. Edit the object as directed.
  7. Click Save.
  8. If directed to do so, restart your server (or servers).


Removing Records from the System Log

The system log captures errors generated by Identity Manager. Periodically, the system log should be truncated to keep it from growing too large. Use the System Log Maintenance Task to remove old records from the system log.

To schedule a task to remove old records from the System Log, follow these steps:

  1. In the Administrator interface, click Server Tasks > Manage Schedule.
  2. In the Tasks Available for Scheduling section, click the System Log Maintenance Task.
  3. The “Create New System Log Maintenance Task Task Schedule” page opens.

  4. Complete the form and click Save.



Previous      Contents      Index      Next     


Part No: 820-2954-10.   Copyright 2008 Sun Microsystems, Inc. All rights reserved.