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.
An example of a restrictive cookie path in IBM® Sterling Business Center is when you will automatically be logged off in the following scenarios: