NOTICE:
The 1.5.x branch is the last generation of Spring Authorization Server. See the OSS and Enterprise support timelines.
Going forward, new features will be added to Spring Security starting in 7.0.
This project replaces the Authorization Server support provided by Spring Security OAuth.
Getting Started
The first place to start is to read the OAuth 2.1 Authorization Framework to gain an in-depth understanding on how to build an Authorization Server. It is a critically important first step as the implementation must conform to the specification defined in the OAuth 2.1 Authorization Framework and the related specifications.
The second place to start is to become very familiar with the codebase in the following Spring Security modules:
-
OAuth 2.0 JOSE (Javascript Object Signing and Encryption)
A significant amount of effort was put into developing the Next Generation OAuth 2.0 Support in Spring Security. The goal is to leverage all the knowledge learned thus far and apply the same to the development of Spring Authorization Server.
Submitted work via pull requests should follow the same coding style/conventions and adopt the same or similar design patterns that have been established in Spring Security’s OAuth 2.0 support.
Building from Source
Spring Authorization Server uses a Gradle-based build system.
In the instructions below, ./gradlew is invoked from the root of the source tree and serves as
a cross-platform, self-contained bootstrap mechanism for the build.