Configuring a restrictive cookie path on WebSphere

Configuring a restrictive cookie path is recommended because when multiple applications are deployed on the same domain and the restrictive cookie path is not set, the user may be automatically logged off from the application when one application sends information to another application. You can configure a restrictive cookie path on WebSphere®.

Procedure

  1. In the WebSphere Administration Console, navigate to the Session Manager > Cookie tab.
  2. In the Cookie tab, set Cookie Path to the context path of your application.

    For example, this would typically be /smcfs, /sbc, and /sfs for the Sterling Warehouse Management System, IBM® Sterling Business Center, and IBM Sterling Field Sales applications, respectively.