Repository files navigation

An OAuth 2.0 & OpenID Connect (OIDC) compliant authorization server just for demo purposes to be used as part of OAuth2/OIDC workshops.

This authorization server should...

• be available for free as open-source
• support efforts to learn OAuth2/OpenID Connect (self-study or as part of workshops)
• provide an easy way for setting up and run it (i.e. without consulting tons of documentation)
• support latest specs and drafts for OAuth 2.x and OpenID Connect
• be provided as docker container & supporttestcontainers

IMPORTANT:
The intention of this project is to be used for demos and as part of trainings/workshops.
It isNOT ready for production use!!

If you are looking for a production-grade identity access management solution please consult thelist ofCertified OpenID provider servers and servicesat theOpenID Foundation.

• RFC 6749: OAuth 2.0 Authorization Framework
• RFC 8252: OAuth 2.0 for Native Apps
• OpenID Connect 1.0
• OAuth 2.0 Grant Flows:
  • Authorization Code Grant (+PKCE)
  • Client Credentials Grant
  • Resource Owner Password Credentials Grant
• RFC 6750: OAuth 2.0 Bearer Token Usage
  • SignedJson Web Tokens (using RSA PKI)
  • Opaque Tokens +OAuth 2.0 Token Introspection
  • OAuth 2.0 Token Revocation
• OpenID Connect Discovery
• JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
• Simple User Access Management API (FollowingSCIM2 standard)
• Simple User Access Management Web UI (Read access only)
• Management of OAuth2/OIDC Clients API
• Management of OAuth2/OIDC Clients Web UI (Read access only)

• OAuth 2.0 Grant Flows:
  • Implicit Grant (Not supported by intention, because ofOAuth 2.0 Security Best Current Practice)
  • OIDC Hybrid Grant Flow (Not supported by intention, because ofOAuth 2.0 Security Best Current Practice as this flow (same as the implicit flow) also returns the id token via the insecure front channel)

• RFC 8628: OAuth 2.0 Device Authorization Grant
• RFC 8693: OAuth 2.0 Token Exchange
• RFC 8707: OAuth 2.0 Resource Indicators
• RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
• OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP)
• The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)
• OAuth 2.0 Pushed Authorization Requests
• OAuth 2.0 Rich Authorization Requests
• JWT Response for OAuth Token Introspection
• OAuth 2.0 Incremental Authorization
• The OAuth 2.1 Authorization Framework

• Q1 2021:Release 1.0 - Mandatory OAuth 2.0 & OIDC grant flows, user and client management, H2 in-memory storage
• Q2 2021:Release 1.1 - Support additional OAuth 2.0 RFCs/Drafts + support other databases for storage

To run the server you need at least a Java 11 JDK or higher (versions 11 and 14 are currently tested).

To run the server just perform agradlew bootrun orrun the Spring Boot starter classcom.example.authorizationserver.AuthorizationServerApplication via your Java IDE.

It is also planned to provide the server as pre-packaged docker container image at a later project stage.

It is planned to provide an integrated user management system via Web UI and Rest API.Currently, the Web UI only supports read-only access atlocalhost:9090/auth/admin.The Rest API also supports creating new users already.

The following predefined users are setup at startup time automatically:

It is planned to provide an integrated client management system via Web UI and Rest API.Currently the Web UI only supports read-only access atlocalhost:9090/auth/admin.The Rest API also supports creating new clients already.

The following predefined clients are setup at startup time automatically:

If you have any feedback on this project this is highly appreciated.

Just send an email toandreas.falk(at)novatec-gmbh.de or contact me via Twitter (@andifalk).

Apache 2.0 licensed