Configuring a restrictive cookie path - overview

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. For example, in Sterling Business Center, you will automatically be logged off in the following scenario:

The image server and the Sterling Business Center application are deployed on the same domain, and you click the Related Tasks link in the Sterling Business Center application.