The Navigation Sessions are used only by the 'Navigation Manager' Web Context (the Muse Navigation Manager component) to store useful data regarding a specific link navigation using a certain target site authentication context (cookies, referrer, next proxy access details, encoding etc.) through Muse Navigation Manager. This type of session is managed using an ID (named MuseSessionID) stored in the path of the Muse Navigation Manager rewritten links. This ID has associated a Navigation Session object at server side that stores the information needed to serve the requests for that Navigation Session (cookies, referrer, authorization, proxy, encoding, etc.).
A Navigation Session is generated by Muse Proxy in the following cases:
- when a user navigates on a 'Type 1' rewritten link there is generated automatically a redirect to a 'Type 2' rewritten link. The 'Type 2' rewritten link generated has associated a new Navigation Session;
- when a user logs into a Muse Proxy application and navigates on a Muse Proxy source link there is generated automatically a redirect to a 'Type 2' rewritten link. The 'Type 2' rewritten link generated has associated a new Navigation Session.
Many Navigation Sessions can be created for a single client, each corresponding to the authentication context of each rewritten target site. All the Navigation Session objects created for a Muse Proxy client are stored inside the Client Session object associated with that client. There is no limit set for the number of Navigation Sessions associated with each client.