m3k-auth - Integration Guide

m3k-auth supports parts of the OAuth 2.0 and OpenID specification. This page contains hints how you add clients and which parts of the spec are expected to work.

New clients must be administratively whitelisted before authorization is possible. You can request a new client_id from Markus Peröbner. Make sure you can fullfil the following restrictions before you ask to be whitelisted.

The OAuth 2.0 redirect_uri must use the https protocol and it must be an absolute URL.

Currently the following OAuth 2.0 scopes are supported:

• openid: This scope requests access to the OpenID Connect (OIDC) user identity information. You can expect sub to contain a persistent, human readable user identifier.

The well-known description of the server can be found in the openid-configuration.