Single Sign-On Implementation \ Frontend integration
When a users logs in for the first time, a cookie is created on the central server. Whenever the users tries to access a second website or application, this website sends a request to the central server to check if the user is already known.
- Accomplished the Backend Integration.
- You are synchronizing the user's data with the OneAll cloud storage.
- You are generating a new
sso_session_tokenwhenever a user logs in.
- You are invaliding the
sso_session_tokenwhen the user logs out.
The library must be present only once on each page. If you have already implemented another of our services, then you might already have added the corresponding code. In this case you can skip this section.
It is compatible with pages served using both HTTP or HTTPS.
// before the path to the library is a protocol-independent absolute path, which detects whether your site uses HTTP or HTTPS.
No modification of the code on secure pages is required.
Our recommendation is to add this code snippet to your website template so that it appears before the closing
</head> tag. As it is loaded asynchronously, you can however add it basically anywhere in your template.
callback_uri when they
switch from one of your websites to another.
Users should now automatically be redirected to your callback script when they switch from one of your websites to another.