Mesogeos Digital Authentication Server
OAuth2 and OpenID Connect — reference, examples and an interactive tester
Everything you need to connect an application to this server: the flows it supports, working code in four languages, and a console that runs the flows against it live.
Start here
Three ways in, depending on what you are doing.
Read the guide
The endpoints, every grant type with a worked request, SSO logout, scopes, security requirements and the error codes you will actually see.
Copy an example
Authorization Code with PKCE and the device flow, in JavaScript, PHP, Python and curl. Complete enough to paste and run.
Try it against this server
Run each flow from the browser with your own client id, watch every request and response, and inspect the tokens that come back.
This server
The values below are this installation's. The discovery document is the one to read from code — it cannot go out of date.
Status
- Issuer
https://auth.mesogeos-digital.com- Environment
- Detecting…
- Reachable
- Checking…
- Version
- Unknown
Endpoints
| Authorization | https://auth.mesogeos-digital.com/oauth/authorize |
| Token | https://auth.mesogeos-digital.com/oauth/token |
| Userinfo | https://auth.mesogeos-digital.com/oauth/userinfo |
| Introspection | https://auth.mesogeos-digital.com/oauth/introspect |
| Revocation | https://auth.mesogeos-digital.com/oauth/revoke |
| Device authorization | https://auth.mesogeos-digital.com/oauth/deviceauthorization |
| Logout | https://auth.mesogeos-digital.com/oauth/logout |
| Discovery | https://auth.mesogeos-digital.com/.well-known/openid-configuration |
| JWKS | https://auth.mesogeos-digital.com/.well-known/jwks.json |
Scopes
What an application may request, and what each one grants.
| Scope | Grants |
|---|---|
profile |
Access to basic profile information (name, picture, locale, etc.). |
email |
Access to the user's primary email address. |
phone |
Access to the user's phone number. |
address |
Access to the user's physical address. |
user |
Access to user account information. |
openid |
Required for OpenID Connect requests — enables the ID Token. |
offline_access |
Allow the application to perform actions on your behalf when you are not online (issues a refresh token). |
system:admin |
Full administrative access — grants all standard scopes. |
system:audit_read |
Read access to audit logs. |
system:health |
Access to system health and monitoring data. |
system:notifications_read |
Read user notifications. |
system:notifications_write |
Send and manage user notifications. |