Provides security cookies to support single sign on and tenant-related information.
The LWSSO cookie contains the tenant and user details and supports single sign-On across the installed solution.
Adds LWSSO token to the URI to support single sign-on when not using LWSSO cookie.
Adds tenant ID to the URI to support multi-tenant environment when not using LWSSO cookie.
Returns the LWSSO cookie by user name.
The LWSSO cookie contains the tenant and user details to support single sign-On across the installed solution.
May be used, for example, when the app calls its backend using REST
Returns the user cookie by user name.
The security cookie contains the tenant and user details to support single sign-on, across the installed solution. The cookie may contain additional security properties if they exist.
This method may be used, for example, when the App calls its backend using REST. For authentication, you must add the current user cookie to the request.
Returns a security request object to send to the back-end.
A request to the back-end system contains the required security data: what security token is needed and where to place it in the request. This method retrieves the appropriate security data.
We differentiate between the token created at login phase, called an incoming token, and the token required to send requests to back-end systems, called an outgoing token. This method returns the suitable security token according the security requirements of the identity management system.
Returns a security request object to send to the back-end.
A request to the back-end system contains the required security data: what security token is needed and where to place it in the request. This method retrieves the appropriate security data.
We differentiate between the token created at login phase, called an incoming token, and the token required to send requests to back-end systems, called an outgoing token. This method returns the suitable security token according the security requirements of the identity management system.