Token Authentication
This is an optional endpoint for token-based authentication.
An example usecase would be logging in the user by a link sent to their email.
Endpoint
Consider the following specs in designing your token authentication endpoint:
| URL | anything |
| Method | POST |
| Headers | Content-Type, Signature |
| Format | JSON |
Parameters
| Attribute | Type | Required |
|---|---|---|
| token | string | Yes |
| ip | string | No |
Response
Status Codes (HTTP)
| Code | Description |
|---|---|
| 200 | Success |
| 401 | Unauthorized |
| 400 | Signature/Input validation Failed |
SSOfy utilizes the HTTP Status code to verify the result.
The response must be of the type Auth Response and include the user object.
📌 Info
Since the authentication is a step before the authorization, it's a good idea to send SSOfy only the user information that is required to be displayed on the login page, such as the user's display name and profile(optional).
Knowledge BaseAt our core, we believe that staying up-to-date with the latest trends and advancements in Authentication and related areas is essential. That's why we take great pride in keeping you informed with the latest insights, updates, and news in this rapidly evolving landscape.
Do you need support?
SSOfy is by Cubelet Ltd.
Copyright © 2024 Cubelet Ltd. All rights reserved.
Copyright © 2024 Cubelet Ltd. All rights reserved.