Configure basic authentication for WebSphere Commerce
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. Basic authentication relies on the assumption that the connection between the client and server computers is secure and can be trusted.Before you beginYou have met the prerequisites listed on the WebSphere Portal integration prerequisites page. About this task- Back up your environment before configuring WebSphere Commerce
and WebSphere Portal:
- Back up your database using the documentation provided by your database provider.
- Disable global security for WebSphere Commerce. If global security is already disabled for WebSphere Commerce, proceed to the next step.
- Depending on your Operating System, complete one of the following
steps:
Log in as the WebSphere Commerce
non-root user.
Ensure that your user has Windows Administrative
user rights.
- Complete one of the following steps:
Stop the WebSphere Commerce test server and
close Rational Application Developer.
- If you are using a stand alone WebSphere Commerce Server environment, start your WebSphere Commerce Server.
- If your WebSphere Commerce configuration is managed by a WAS deployment manager, ensure that the following are
started:
- From your WebSphere Commerce machine, run the following command:
- WC_installdir/components/wcportal/bin/enableWCPortalWizard.sh
- WC_installdir/components/wcportal/bin/enableWCPortalWizard.bat
- WCDE_installdir/components/wcportal/bin/enableWCPortalWizard.bat
For managed, or unmanaged server environments, running this tool will restart your WebSphere Commerce enterprise application. This action will cause downtime for your site.
From your Windows machine, map to the i5/OS machine,
and run the following command:
- WC_installdir/components/wcportal/bin/enableWCPortalWizard.os400.bat
- 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 required 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.
- On the Authentication mechanism for Single
Sign-On page, select Basic Authentication.
- Complete your LDAP configuration information on the LDAP information
page and click Next.
- 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.
- The Summary page displays the options you selected. Verify that this information is correct, and click Next.
- 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
- WCDE_installdir/logs/wcportalconfig_ timestamp.log
If you are using WAS
6.1, complete all the steps marked with the WAS 6.1 tag in Configuring
Member Manager before proceeding to Step 12.
- Set the Server connection type and port field:
- Start the WebSphere Commerce Developer.
- From within Rational Application Developer, click on the WebSphere Commerce Test Server in the Servers tab.
- Expand the Server section and ensure that the Server connection type and port field is set to SOAP.
- Save the configuration and exit.
- Re-enable global security, if you disabled
it in Step 3. See Enabling
security with an LDAP user registry.
- Republish the WebSphere Commerce project:
- From within Rational Application Developer, right-click on the WebSphere Commerce Test Server in the Servers tab and select Start.
- Right-click the WebSphere Commerce Test Server and publish the EAR file by clicking Publish.
Restart WAS if you receive an error message such as Failed to get WMM Member Service.
- Test the WebSphere Commerce configuration by logging into the WebSphere Commerce administration console using the WebSphere Commerce administrator ID and password.
- After your WebSphere Commerce Server is restarted, open a Web
browser and verify that the following URLs open properly:
- For 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
- For 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.
- (optional) Configure LDAP server access over SSL.
- Next step:Install the WebSphere Commerce sample portal application.