Administering WSRP Consumers for Portal Server

This section explains the tasks that need to be performed to configure Portal Server to consume remote portlets offered by the producer.

To Navigate to the WSRP Consumer Options in the Portal Server Administration Console

1. Log in to the Portal Server administration console.

2. Click the portal name hyperlink.

3. Click the WSRP tab.

To Add a Configured Producer

1. If you are not on the Producer tab, see To Navigate to the WSRP Consumer Options in the Portal Server Administration Console.

2. Select DN (Distinguished Name). Click New to create a new configured producer.

3. Type the configured producer name. Select the identity propagation mechanism. By default, None is selected.

   An identity propagation mechanism allows the users of the consumer portal to present their credentials to the producer portal and allows the users federate their identity from the consumer portal to the producer portal. For more details on identity propagation mechanism, see Identity Propagation Mechanism.

4. Type the WSDL URL and click Next.

   ---

   Note –

   You can search for a WSDL URL based on the producer or portlet if you do not know the WSDL url of the producer. The search result displays WSDL URL of a producer only if the producer is published. For more information on how to search for a producer using the command line interface, see To Search for a Producer Details.

   ---

5. (Optional) If the producer requires registration, you can register the producer in two methods:

   • Enter the registration property values (in-band registration)

   • Enter the registration handle (out-of-band registration)

6. Click Next.

7. If you selected the first method in step 7, enter the registration properties and click Next. If you selected the second method, enter the registration handle obtained through out-of-band communication, and click Next.

8. Review the details and click Finish.

To Create Channels to Display Remote Portlets on the Portal Desktop

1. Log in to the Portal Server administration console.

2. Click the portal name hyperlink.

3. Select the DN on which you want to create a remote portlet.

4. Click Manage Channels and Containers.

5. Select the container to which you want the remote portlet to appear.

6. Click New Channel or Container on the right tab.

   A wizard appears.

7. Select portal, DN, and Channel.

8. Click Next and select WSRP Remote Portlet Channel.

9. Click Next.

   The screen displays the list of available configured producers.

10. Select the configured producer and click Next.

    The Remote Portlet list displays the list of remote portlets that the producer offers.

11. Select the remote portlet and click Next.

12. Provide a local channel name for the remote portlet.

13. Click Finish to create a remote portlet on your portal desktop.

    Log in to portal desktop as a user and select the container or tab on which you created the remote portlet. The portlet is visible on your portal page.

To Access a Producer Trough a Gateway

1. In a text editor, edit the following file:

   /var/opt/SUNWappserver/domains/domain1/config/domain.xml

2. Set the following JVM options: Dhttp.proxyHost, Dhttp.proxyPort, Dhttp.proxyUser, and Dhttp.proxyPassword.

3. Save the file.

To Update the Service Description

1. If you are not on the Consumer tab, see To Navigate to the WSRP Consumer Options in the Portal Server Administration Console.

2. Select DN (Distinguished Name).

3. Click the configured producer hyperlink.

4. In the Edit Configured Producer screen, click Update Service Description.

5. Check the local repository/cache for the new portlets offered by this producer.

6. Create a new channel to see if any new portlets are offered by the producer.

To Export Roles as User Categories in Producer

1. In the Access Manager administrator console, create a role and add a user.

2. While deploying the portlet in webxml of the portlet application, add the following code:

   <security-role> <role-name>PS_TEST_DEVELOPER_ROLE<role-name> </security-role>

3. Add the following lines in the portlet.xml file of the portal.

   <security-role-ref> <role-name>PS_TEST_DEVELOPER_ROLE<role-name> <role-link>PS_TEST_DEVELOPER_ROLE<role-link> </security-role-ref>

4. Create the portlet application war file.

5. Create a roles file with the following entry.

   cn\=AM_TEST_DEVELOPER_ROLE,o\=PortalSample,dc\=domain, dc\=domain,dc\=com=PS_TEST_DEVELOPER_ROLE

6. Deploy the portlet using the following command.

   /opt/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f ps-password -d "o=PortalSample,dc=domain,dc=domain,dc=com"-p portal1 -i portlet-name --rolesfile roles-file test-portlet-war-file

   This task deploys a portlet. All roles associated with the portlet are automatically exported as user categories in the producer.

To Map User Categories to a Role

1. If you are not on the Consumer tab, see To Navigate to the WSRP Consumer Options in the Portal Server Administration Console.

2. In the Consumer tab, click the configured producer name hyperlink.

   User Category displays the roles in the producer portlet. Local Roles displays the roles that are defined for the consumer's Access Manager.

3. In the User Categories to Role Mapping section, map user categories to the roles defined at the consumer

4. Click OK to save the details.

Mapping Consumer Attributes

The producer does not have any real user identity and does not have any data associated with the user. The consumer propagates the common user details known as user profiles. The consumer chooses some of the common attributes such as name, address, and so on and optionally propagates these attributes to the producer. The producer can generate some meaningful data based on the user.

The Portal Server implementation of WSRP Consumer maps common user attributes stored in the user entry on the Sun Java System Directory Server to the standard set of user attributes that the WSRP specification mandates.

If a consumer portlet uses any of the attributes that are not specified in the LDAP schema, create a custom object class to store these attributes and add this object class to the user entry. After you create the attributes, map the LDAP attribute to the corresponding WSRP attribute using Sun Java System Access Manager administrator console. Mapping the LDAP attribute to the corresponding WSRP attribute allows the consumer to propagate custom user profile data that might be required by the producer.

Identity Propagation Mechanism

Identity propagation is a mechanism by which the WSRP consumer supplies the identity of the user to the WSRP producer web service. Users federate their identity between the consumer and producer. After a successful federation, the consumer portal propagates the user identity to the producer portal. The WSRP producer, after receiving the user credentials from the consumer, validates the credentials and allows or denies access to the resource in the specified user context.

The user has two identities for each portal: one for producer portal and the other for the consumer portal. Users federate these identities using the identity propagation mechanism, which provides single-sign on for the consumer and the producer portal. When the user logs into the portal through the consumer portal, the user gets the content that the user gets when logs directly into the producer portal. The changes that the user makes using the federated identity would be available when the user logs into the producer portal.

Identity Propagation Mechanism at the Consumer of Portal Server

The consumer can set the identity propagation because the consumer has knowledge about end users. There are two phases in setting up the identity propagation:

Administrator Setup: Administrator of the consumer portal discovers that the producer supports specific identity propagation mechanisms. Then, the administrator set up the system that allows the user to use identity propagation.

User Setup: The end user federates its identity by populating the credentials.

The WSRP Producer available through Portal Server supports the following identity propagation mechanisms:

• SSO Token: Select if both the producer portal and the consumer portal are connected to the same Access Manager instance. Use when both the producer portal and consumer portal are deployed within the same organization. This option does not allow the end user to federate the identity because user identity from consumer and producer is accepted by the same Access Manager instance. This mechanism is not interoperable with other portal vendors.

• WSS User Name Token Profile (Username only): Uses the WSS specification where the user name is propagated as WS Security headers from the consumer portal to the producer portal.

• WSS User Name Token Profile (With password digest): WS Security headers send the user ID that is targeted at the producer with the password in the Digest form.

• WSS User Name Token Profile (With password text): WS Security headers send the user's user ID that is targeted at the producer with the password in the Text form.

• No Identity Propagation: This is the default behavior of WSRP as specified by the WSRP specification. This is the default option in Portal Server. A consumer created by default settings does not have identity propagation.

In the above list, WSS User Name Token Profile (Username only), WSS User Name Token Profile (With password digest), and WSS User Name Token Profile (With password text) implement the OASIS WSS Username token profile specification. This specification describes how to use the Username Token with web Services. The WSS specification describes how a web service consumer can supply a Username Token by identifying the requestor by username, and optionally using a password to authenticate that identity to the web service producer.

After the consumer is created, the administrator has to create remote channels based on the identity propagation mechanism supported by the consumer. After the channels are available on the user desktop, they are ready to accept identity propagation.

To Create User Credentials Using WebServices SSO Portlet

1. Log in to Portal Server.

2. In the WebServices SSO Portlet section, click Edit.

3. In the Create NewToken Profile section, select the WebService URL for which you want to create a user token profile.

4. Type the user name and password. Click Add to add the user name and password.

   You can also edit or remove an existing user token profile.

Identity Propagation at Producer

The identity propagation mechanism is set at the producer automatically. Portal Server supports the following identity propagation mechanisms: Sun SSO Token, OASIS user name token (all its variants), and No identity propagation.

Configuring the Sun Java System WSRP Producer to Accept Digest Passwords

• Only the newly created users, after running the configuration command to store the LDAP passwords in plain text, are able to use the Digest Password facility.

• Creation of a consumer involves selecting the WSSO Username Token Profile (with Digest Password) option for User Identity Propagation Mechanism.

• The Web Services SSO Portlet must be edited to select the appropriate Web service URL (producer) and the newly created username and password must be provided.

To Configure the Sun Java System WSRP Producer to Accept Digest Passwords

1. Run the following command to change the password storage scheme of the Directory Server so that plain text passwords are stored.

   /opt/SUNWdsee/ds6/bin/dscfg set-server-prop pwd-storage-scheme:CLEAR

2. Create a new user in the Access Manager console to ensure that the Username Token Profile with Password Digest can be used.

Best Practices for Using Identity Propagation Mechanism

• When using the WSS User Name Token Profile (With password text), make sure that the communication between the producer portal and consumer portal is secure, because the password is sent in plain text between the consumer and the producer.

• Do not have two different consumers that point to the same producer URL using different identity propagation mechanism types.

• Do not switch to another identity propagation mechanism after a consumer has been created and is using an identity propagation mechanism, because the user's portlets preferences are stored based on the identification of the user, and switching to another identity propagation results in a loss of user customization.