Configuring basic authentication for WebSphere Commerce

Basic authentication is an authentication method that is designed to allow client programs to provide credentials. These credentials are in the form of a user name and password when a request is made. Basic authentication relies on the assumption that the connection between the client and server computers is secure and can be trusted.

Before you begin

Ensure that your system meets the prerequisites that are listed on the WebSphere Portal integration prerequisites page.

Procedure

  1. Back up your environment before you configure WebSphere Commerce and WebSphere Portal:
  2. Back up your database using the documentation that is provided by your database provider.
  3. Disable global security for WebSphere Commerce. If global security is already disabled for WebSphere Commerce, proceed to the next step.
  4. Depending on your Operating System, complete one of the following steps:
    • SolarisLinuxAIX Log in as the WebSphere Commerce non-root user.
    • Windows Ensure that your user has Windows Administrative user rights.
  5. Complete one of the following steps:
  6. From your WebSphere Commerce machine, run the following command:
    • SolarisLinuxAIXWC_installdir/bin/WCIntegrationWizard.sh
    • WindowsWC_installdir/bin/WCIntegrationWizard.bat
    • WebSphere Commerce DeveloperWCDE_installdir/bin/WCIntegrationWizard.bat
      Note: For managed, or unmanaged server environments, running this tool restarts your WebSphere Commerce Enterprise application. This action causes downtime for your site.
    • For IBM i OS operating system From your Windows machine, map to the IBM i machine, and run the following command:
      • WC_installdir/bin/WCIntegrationWizard.os400.bat
      • For IBM i OS operating system On the Logon Information page, enter the System Name, User Profile, and Password for the iSeries system on which you are configuring WebSphere Portal. Ensure that the user profile has QSECOFR class authority. Click Next.
      • Review the prerequisites on the first page of the wizard, and click Next.
      • The WebSphere Commerce site information page appears. Select your WebSphere Commerce instance from the dropdown list, and provide your WebSphere Commerce database password. This password is the database schema owner's password. Click Next.
  7. WebSphere Commerce Developer On the Authentication mechanism for Single Sign-On page, select Basic Authentication.
  8. Complete your LDAP configuration information about the LDAP information page and click Next.
    Note:
    • The DN should not contain any spaces before or after the comma (,) or equals sign (=) and must be entered in lowercase.
    • It is not possible to set passwords for users between WebSphere Commerce, WebSphere Portal Server, and Microsoft Active Directory until the secure socket layer is enabled. You must use the ldapPort to 636 for this step.
  9. The Summary page displays the options that you selected. Verify that this information is correct, and click Next.
  10. When the configuration is complete, the wizard displays the result of the configuration, and the location of the log files. Click Finish to exit the wizard. The log files are found in the following location:
    • WC_installdir/instances/ instance_name/logs/wcportalconfig_timestamp.log
    • WebSphere Commerce DeveloperWCDE_installdir/logs/wcportalconfig_ timestamp.log
  11. WebSphere Commerce DeveloperSet the Server connection type and port field:
    1. Start the WebSphere Commerce Developer.
    2. From within Rational Application Developer, click the WebSphere Commerce Test Server in the Servers tab.
    3. Expand the Server section and ensure that the Server connection type and port field is set to SOAP.
    4. Save the configuration and exit.
  12. Re-enable global security, if you disabled it in Step 3. See Enabling WebSphere global security.
  13. WebSphere Commerce DeveloperRepublish the WebSphere Commerce project:
    1. From within Rational Application Developer, right-click on the WebSphere Commerce Test Server in the Servers tab and select Start.
    2. Right-click the WebSphere Commerce Test Server and publish the EAR file by clicking Publish.
    Note: Restart WebSphere Application Server if you receive an error message such as Failed to get WMM Member Service.
  14. Test the WebSphere Commerce configuration by logging in to the Administration Console using the WebSphere Commerce administrator ID and password.
  15. After your WebSphere Commerce Server is restarted, open a web browser and verify that the following URLs open properly:
    • For IBM i OS operating systemSolarisLinuxAIXWindowsFor the server environment:
      • OrderServices: http://hostname:8007/webapp/wcs/component/order/services/OrderServices
      • MemberServices: http://hostname:8007/webapp/wcs/component/member/services/MemberServices

      • ContractServices: http://hostname:8007/webapp/wcs/component/contract/services/ContractServices

      • CatalogServices: http://hostname:8007/webapp/wcs/component/catalog/services/CatalogServices
      • BusinessContextServiceWrapperService: https://hostname:8000/Enablement-BusinessContextWebServicesRouter/services/BusinessContextServiceWrapper
    • WebSphere Commerce DeveloperFor the development environment:
      • OrderServices: http://hostname:80/webapp/wcs/component/order/services/OrderServices
      • MemberServices: http://hostname:80/webapp/wcs/component/member/services/MemberServices
      • ContractServices: http://hostname:80/webapp/wcs/component/contract/services/ContractServices
      • CatalogServices: http://hostname:80/webapp/wcs/component/catalog/services/CatalogServices
      • BusinessContextServiceWrapperService:
        • https://hostname:8000/Enablement-BusinessContextWebServicesRouter/services/BusinessContextServiceWrapper
        • http://hostname:80/Enablement-BusinessContextWebServicesRouter/services/BusinessContextServiceWrapper
        Where:
        hostname
        Is the host name of the WebSphere Commerce machine.
  16. Optional: Configure LDAP server access over SSL.

What to do next

Install the WebSphere Commerce sample portal application.