Now that the asset has been created, you must provide proxy authentication information to access the asset at the role level.
Before any proxy authentication information can be returned for a user, you must grant READ permission on the asset. If the asset does not have READ permission, it does not matter what kind of proxy authentication information is set up at the subject, role, or asset level—no information can be returned for a user.
Creating user-based proxy
authentication information
Before you can create proxy authentication information, users and assets must exist in the enterprise environment. To define a user’s proxy authentication information for an asset:
In the Manage User Proxy Authentication Information dialog box, click New. The Create User Proxy Authentication Information dialog box displays.
Enter:
Asset DN – the distinguished name (DN) for the asset. To look up the DN, click Find.
In the Choose Asset dialog box, select the organization to which the asset belongs, highlight the asset name, then click OK. The asset DN displays in the Create User Proxy Authentication Information dialog box.
Service URL – the connection request uses this URL to establish a connection with the selected asset.
User Name – the name used to log in to the asset specified by the URL.
Password – a valid password for the user name.
Verify Password – the same password.
Click OK to save your changes. The asset now has proxy authentication information associated with it.
Repeat this procedure for each asset for which you want to create proxy authentication information.
The role-level proxy authentication information has been created. The next section describes the ProxyAuth.jsp that uses the proxy authentication information.
