The User Application install enables you to set User Application configuration parameters. Most of these parameters are also editable with configupdate.sh or configupdate.bat after installation; exceptions are noted in the parameter descriptions. For a cluster, specify identical User Application configuration parameters for each member of the cluster.
Click
through the first User Application Configuration page.Set the basic User Application configuration parameters described in Table Table 6-1, then continue with Step 3.
Table 6-1 User Application Configuration: Basic Parameters
If you want to set additional User Application configuration parameters, click Table 6-2 describes the Advanced Options parameters. If you do not want to set additional parameters described in this step, skip to Step 4.
. (Scroll to view the whole panel.) TableTable 6-2 User Application Configuration: All Parameters
Type of Setting |
Field |
Description |
---|---|---|
eDirectory Connection Settings |
|
Required. Specify the hostname or IP address for your LDAP server. For example: myLDAPhost |
|
Specify the non-secure port for your LDAP server. For example: 389. |
|
|
Specify the secure port for your LDAP server. For example: 636. |
|
|
Required. Specify the credentials for the LDAP Administrator. This user must already exist. The User Application uses this account to make an administrative connection to the Identity Vault. This value is encrypted, based on the master key. |
|
|
Required. Specify the LDAP Administrator password. This password is encrypted, based on the master key. |
|
|
Allows users who are not logged in to access the LDAP Public Anonymous Account. |
|
|
Allows users who are not logged in to access permitted portlets. This user account must already exist in the Identity Vault. To enable LDAP Guest, you must deselect . To disable Guest User, select . |
|
|
Specify the LDAP Guest password. |
|
|
Select this option to require that all communication using the admin account be done using a secure socket. (This option can have adverse performance implications). This setting allows other operations that don't require SSL to operate without SSL. |
|
|
Select this option to require that all communication done on the logged-in user's account be done using a secure socket. (This option can have severe adverse performance implications). This setting allows other operations that don't require SSL to operate without SSL. |
|
eDirectory DNs |
|
Required. Specify the LDAP distinguished name of the root container. This is used as the default entity definition search root when no search root is specified in the directory abstraction layer. |
|
Required. Specify the distinguished name of the User Application driver. For example, if your driver is UserApplicationDriver and your driver set is called myDriverSet, and the driver set is in a context of o=myCompany, you type a value of: cn=UserApplicationDriver,cn=myDriverSet,o=myCompany |
|
|
Required. An existing user in the Identity Vault who has the rights to perform administrative tasks for the User Application user container specified. This user can use the tab of the User Application to administer the portal.If the User Application Administrator participates in workflow administration tasks exposed in iManager, Novell Designer for Identity Manager, or the User Application ( IDM User Application: Administration Guide for details. tab), you must grant this administrator appropriate trustee rights to object instances contained in the User Application driver. Refer to theTo change this assignment after you deploy the User Application, you must use the pages in the User Application. |
|
|
The Provisioning Application Administrator manages Provisioning Workflow functions available through the tab of the User Application. This user must exist in the Identity Vault prior to being designated the Provisioning Application Administrator.To change this assignment after you deploy the User Application, you must use the pages in the User Application. |
|
Meta-Directory User Identity |
|
Required. Specify the LDAP distinguished name (DN) or fully qualified LDAP name of the user container. This defines the search scope for users and groups. Users in this container (and below) are allowed to log in to the User Application. IMPORTANT:Be sure the User Application Administrator specified during User Application driver setup exists in this container if you want that user to be able to execute workflows. |
|
The LDAP user object class (typically inetOrgPerson). |
|
|
The LDAP attribute (for example, CN) that represents the user’s login name. |
|
|
The LDAP attribute used as the identifier when looking up users or groups. This is not the same as the login attribute, which is used only during login, and not during user/group searches. |
|
|
Optional. The LDAP attribute that represents the user’s group membership. Do not use spaces in this name. |
|
|
|
This role is available in the Novell Identity Manager Roles Based Provisioning Module. This role allows members to create, remove, or modify all roles, and grant or revoke any role assignment to any user, group, or container. It also allows its role members to run any report for any user. By default, the User Application Admin is assigned this role. To change this assignment after you deploy the User Application, use the page in the User Application. |
Meta-Directory User Groups |
|
Required. Specify the LDAP distinguished name (DN) or fully qualified LDAP name of the group container. Used by entity definitions within the directory abstraction layer. |
|
The LDAP group object class (typically groupofNames). |
|
|
The attribute representing the user’s group membership. Do not use spaces in this name. |
|
|
Select this option if you want to use dynamic groups. |
|
|
The LDAP dynamic group object class (typically dynamicGroup). |
|
eDirectory Certificates |
|
Required. Specify the full path to your keystore ( cacerts) file of the JRE that the application server application server is using to run, or else click the small browser button and navigate to the cacerts file. The User Application installation modifies the keystore file. On Linux or Solaris, the user must have permission to write to this file. |
|
Required. Specify the cacerts password. The default is changeit. |
|
Private Key Store |
|
The private keystore contains the User Application’s private key and certificates. Reserved. If you leave this empty, this path is /jre/lib/security/cacerts by default. |
|
This password is changeit unless you specify otherwise. This password is encrypted, based on the master key. |
|
|
This alias is novellIDMUserApp unless you specify otherwise. |
|
|
This password is nove1lIDM unless you specify otherwise. This password is encrypted, based on the master key. |
|
Trusted Key Store |
|
The Trusted Key Store contains all trusted signers’ certificates used to validate digital signatures. If this path is empty, the User Application gets the path from System property javax.net.ssl.trustStore. If the path isn’t there, it is assumed to be jre/lib/security/cacerts. |
|
If this field is empty, the User Application gets the password from System property javax.net.ssl.trustStorePassword. If the value is not there, changeit is used. This password is encrypted, based on the master key. |
|
Novell Audit Digital Signature and Certificate Key |
|
Contains the Novell Audit digital signature key and certificate. |
|
|
Displays the digital signature certificate. |
|
|
Displays the digital signature private key. This key is encrypted, based on the master key. |
Access Manager and iChain Settings |
|
If this option is selected, the User Application supports simultaneous logout of the User Application and either Novell Access Manager or iChain. The User Application checks for a Novell Access Manager or iChain cookie on logout and, if the cookie is present, reroutes the user to the ICS logout page. |
|
The URL to the Novell Access Manager or iChain logout page, where the URL is a hostname that Novell Access Manager or iChain expects. If ICS logging is enabled and a user logs out of the User Application, the user is rerouted to this page. |
|
|
|
Specify the application server hosting the Identity Manager User Application. For example: myapplication serverServer This value replaces the $HOST$ token in e-mail templates. The URL that is constructed is the link to provisioning request tasks and approval notifications. |
|
Used to replace the $PORT$ token in e-mail templates used in provisioning request tasks and approval notifications. |
|
|
Used to replace the $SECURE_PORT$ token in e-mail templates used in provisioning request tasks and approval notifications. |
|
|
Refers to a non-secure protocol, HTTP. Used to replace the $PROTOCOL$ token in e-mail templates used in provisioning request tasks and approval notifications. |
|
|
Refers to a secure protocol, HTTPS. Used to replace the $SECURE_PROTOCOL$ token in e-mail templates used in provisioning request tasks and approval notifications. |
|
|
Specify e-mail from a user in provisioning e-mail. |
|
|
Specify the SMTP e-mail host that provisioning e-mail is using. This can be an IP address or a DNS name. |
|
Password Management |
|
|
|
This feature enables you to specify a Forgot Password page residing in an external Forgot Password WAR and a URL that the external Forgot Password WAR uses to call back the User Application through a Web service. If you select , you must supply values for and .If you do not select /jsps/pwdmgt/ForgotPassword.jsf (without the http(s) protocol at the beginning). This redirects the user to the Forgot Password functionality built into the User Application, rather than to an external WAR. IDM uses the default internal Password Management functionality, . |
|
|
This URL points to the Forgot Password functionality page. Specify a ForgotPassword.jsf file in an external or internal password management WAR. |
|
|
|
If you are using an external password management WAR, supply the path that the external Password Management WAR uses to call back the User Application through Web Services, for example https:// idmhost:sslport/idm . |
Miscellaneous |
|
The application session timeout. |
|
If the client installation uses the On-Line Certificate Status Protocol (OCSP), supply a Uniform Resource Identifier (URI). For example, the format is http://host:port/ocspLocal. The OCSP URI updates the status of trusted certificates online. |
|
|
Fully qualified name of the authorization configuration file. |
|
|
|
|
|
|
|
Container Object |
|
Select each Container Object Type to use. |
|
Select from the following standard containers: locality, country, organizationalUnit, organization, and domain. You can also define your own containers in iManager and add them under . |
|
|
Lists the Attribute Type name associated with the Container Object Type. |
|
|
Specify the LDAP name of an objectclass from the Identity Vault that can serve as a container. For information on containers, see the Novell iManager 2.6 Administration Guide . |
|
|
Supply the attribute name of the container object. |
After you finish configuring the settings, click Section 6.10, Verify Choices and Install.
, then continue with