Skip to main content

Sessions

Sessions​

Summary​

SAP session cookies now get passed through API Proxy functionality. These cookies have their values encrypted to prevent tampering or usage outside Link. Using sessions enables the caching of Variant Configuration data to improve the performance of VC requests.

Using Sessions​

session header parameter​

For session functionality, there is a new session header parameter. This header accepts two values:

  • Keep: When the session: keep is included in a request, and no session cookie is provided, Link will establish a new session with SAP for the user and return the SAP session cookies with encrypted values. If the header is included with session cookies, the existing session will be used and maintained for the request.

  • End (Default): When the session: end is included in a request, or when no session header is provided, Link will not maintain any session with SAP. If a session cookie is provided, the related session will be terminated.

session-id header parameter​

The session-id header parameter is optional, and if provided, the value should be 10-byte alphanumeric (ex K9b2W4v7mX). This header along with the session header will help manage the session effectively. This feature enables users to work across multiple browser tabs with isolated data sessions to compare different configurations simultaneously without cross-tab interference.