Deprecated feature

Configuring basic authentication for WebSphere Portal

Note: Basic Authentication is only supported when Application Security is disabled. Basic Authentication has been deprecated in WebSphere Commerce integration with WebSphere Portal. It is strongly recommended to migrate to the suggested LTPA configuration.

See Configuring WebSphere Portal with WebSphere Commerce for more information.

Basic authentication is an authentication method that is designed to allow client programs to provide credentials - in the form of a user name and password - when making a request. Although the scheme is easily implemented, it relies on the assumption that the connection between the client and server computers is secure and can be trusted.

Before you begin

Procedure

  1. From your WebSphere Commerce machine, create the MVCPortletExt.jar file for use with the WebSphere Application Server JAAS component:
    1. Create a copy of Foundation-Portal-Core.jar and name this new file as MVCPortletExt.jar from the following location:
      • WC_installdir/portal/WEB-INF/lib/Foundation-Portal-Core.jar
      • WCDE_installdir/portal/WEB-INF/lib/Foundation-Portal-Core.jar
    2. Modify this new file, MVCPortletExt.jar, to make it contain only the following class and remove all other contents:
      • com.ibm.commerce.foundation.internal.client.portal.modules.MVCPortletLoginModule
  2. Copy this new file, MVCPortletExt.jar, to the Java_home/lib/ext directory on your WebSphere Portal machine.
    Note: If you plan to integrate WebSphere Commerce into a WebSphere Portal clustered environment, copy the MVCPortletExt.jar file to the Java_home/lib/ext directory of each WebSphere Portal node.
  3. Open the WebSphere Application Server administrative console:
  4. Click Security > Global Security . From the Java Authentication and Authorization Service section, select Application logins.
  5. Click Portal_LTPA,.
  6. Select New to create a new module.
    1. In the Module class name field, type com.ibm.commerce.foundation.internal.client.portal.modules.MVCPortletLoginModule. Accept the default settings for the remaining fields.
    2. Select OK to confirm the module settings.
    3. Save the configuration.
  7. Click Resources > Resource Environment Providers. Ensure that the scope is set at the node level for a stand alone WebSphere Portal server, or at the cluster level for a WebSphere Portal clustered environment.
  8. Click WP AuthenticationService. Under Additional Properties select Custom Properties.
    1. Click New to create new custom properties.
    2. In the Name field, type authentication.basic.login.target.
    3. In the Value field, type Portal_LTPA.
    4. Click OK to confirm the changes.
    5. Save the configuration.
  9. Restart the WebSphere Portal Server.

What to do next

Configure the sample portlets.