3.1 Using Designer to Create and Configure the Driver

The following sections provide steps for using Designer to create and configure a new SAP Portal driver. For information about using iManager to accomplish these tasks, see Section 3.2, Using iManager to Create and Configure the Driver.

3.1.1 Using Designer to Import the Driver Configuration File

Importing the SAP Portal driver configuration file creates the driver in the project and adds the policies needed to make the driver function properly.

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver set where you want to create the driver, then select New > Driver to display the Driver Configuration Wizard.

  3. In the Driver Configuration list, select SAP Portal, then click Run.

  4. On the Import Information Requested page, fill in the following fields:

    • Driver Name: Specify a name that is unique within the driver set.

    • URL of the remote SPML Provisioning Service Point: Specify the URL of the remote SAP Portal SPML Provisioning Service Point.

      For example: http://my.sap.com:50000/spml/spmlservice

    • Authentication ID: Specify the authentication ID for the remote SAP Portal SPML Provisioning Service Point. For more information, see Section 5.1, Creating an Administrative User Account for the Driver.

    • Use User Account Entitlement: Select True if you have entitlements enabled in your environment. Select False if entitlements are not enabled. The SAP Portal driver contains three preconfigured entitlements. For more information, see Section 4.0, Implementing the Preconfigured Entitlements.

    • User Container: Specify the Identity Vault top level container where the users objects are monitored for Subscriber events. This value is used for all drivers and is stored on the driver set. If you want a different location for each driver, create a driver level GCV parameter with the same name.

    • Group Container: Specify the Identity Vault top level container where the groups are monitored for Subscriber events. This value is used for all drivers and is stored on the driver set. If you want a different location for each driver, create a driver level GCV parameter with the same name.

    • Driver is Local/Remote: Select whether the driver is running locally or is using the Remote Loader. For more information, see the Identity Manager 3.6.1 Remote Loader Guide.

    • Enter the password for the Authentication Password: Specify the password for the Authentication ID, then reenter the password for verification.

    • Enter the password to Reset Password: Specify a default password to be set for users when the driver resets a user’s password in the SAP Portal. It is set during password changes if the user-supplied password is not accepted by the SAP server. This is only used if the driver resets the password.

      The password must comply with your SAP Portal Security Policy for passwords. The default SAP Portal Security Policy requires alphanumeric passwords between 5 and 14 characters in length.

  5. Click Next to import the driver configuration.

    At this point, the driver is created from the basic configuration file. To ensure that the driver works the way you want it to for your environment, you must review and modify (if necessary) the driver’s default configuration settings.

  6. To modify the default configuration settings, click Configure, then continue with the next section, Using Designer to Adjust the Driver Settings.

    or

    To skip the configuration settings at this time, click Close. When you are ready to configure the settings, continue with the next section, Using Designer to Adjust the Driver Settings.

  7. Continue with Section 3.1.3, Using Designer to Deploy the Driver, to deploy the driver into the Identity Vault.

3.1.2 Using Designer to Adjust the Driver Settings

The information specified on the Import Information Requested page is the minimum information required to import the driver. However, the base configuration might not meet your needs, or you might need to change the configuration you created when you imported the driver.

  • You might need to change whether the driver is running locally or remotely.

  • You might need to change whether the driver is using entitlements.

If you need to do additional configuration for the driver, you must access the properties page of the driver. If you do not have the Driver Properties page displayed:

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver icon Driver icon or the driver line, then select Properties.

    This opens the properties page for the driver. Use the information in Section A.0, Driver Properties to adjust the configuration.

3.1.3 Using Designer to Deploy the Driver

After a driver is created in Designer, it must be deployed into the Identity Vault.

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver icon Driver icon or the driver line, then select Live > Deploy.

  3. If you are authenticated to the Identity Vault, skip to Step 5; otherwise, specify the following information to authenticate:

    • Host: Specify the IP address or DNS name of the server hosting the Identity Vault.

    • Username: Specify the DN of the user object used to authenticate to the Identity Vault.

    • Password: Specify the user’s password.

  4. Click OK.

  5. Read through the deployment summary, then click Deploy.

  6. Read the successful message, then click OK.

  7. Click Define Security Equivalence to assign rights to the driver.

    The driver requires rights to objects within the Identity Vault. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.

    1. Click Add, then browse to and select the object with the correct rights.

    2. Click OK twice.

  8. Click Exclude Administrative Roles to exclude users that should not be synchronized.

    You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.

    1. Click Add, then browse to and select the user object you want to exclude.

    2. Click OK.

    3. Repeat Step 8.a and Step 8.b for each object you want to exclude.

    4. Click OK.

  9. Click OK.

3.1.4 Using Designer to Start the Driver

When a driver is created, it is stopped by default. You must start the driver before events are processed.

To start the driver after the driver is deployed:

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver icon Driver icon or the driver line, then select Live > Start Driver.

For information about management tasks with the driver, see Section 7.0, Managing the Driver.