OpenID Connect (OIDC) is an identity layer built on top of the OAuth 2.0 protocol. It allows clients (applications) to verify the identity of end-users based on the authentication performed by an authorization server and to obtain basic profile information about the end-user in an interoperable and REST-like manner.
We have written a developer guide to accompany these API endpoints.
Implementing OIDC with Edlink
Developer Guide
Click to Read
Key Concepts
| Concept | Description |
|---|---|
| Authorization Server | The server that authenticates the user and issues tokens. |
| Client | The application requesting access to the user's resources. |
| ID Token | A JSON Web Token (JWT) that contains user profile information. |
| Access Token | A token used to access protected resources. |
| Refresh Token | A token used to obtain a new access token. |
Available Endpoints
| Endpoint | Description |
|---|---|
| Authorization Endpoint | Used to obtain an authorization grant from the user. |
| Token Endpoint | Used to exchange an authorization grant for tokens. |
| Userinfo Endpoint | Used to retrieve user profile information. |
| JWKS Endpoint | Provides the public keys needed to verify tokens. |
| Introspection Endpoint | Used to check the validity of tokens. |
| Revocation Endpoint | Used to invalidate tokens. |
| Well-Known Configuration | Provides metadata about Edlink's OIDC provider. |