Remote validation using token introspection

As an OAuth provider can be deployed as separate entities, the Resource Server should be able to validate access tokens by querying directly at a shared database or even by asking the Authorization Server through an available endpoint. To support this approach, the community has created an OAuth 2.0 profile called OAuth 2.0 Token Introspection, defined by the RFC 7662 specification which is available at https://tools.ietf.org/html/rfc7662. This recipe will present how to enable the Authorization Server to support the /oauth/check_token endpoint and how to configure RemoteTokenServices at the Resource Server, which can be used to remotely validate any presented access token.

Getting ready

Because of the usage of remote token validation, you will need to create two separate applications for the Authorization Server and the Resource Server. Both applications will rely on the database to store and share the Resource Owner's information instead of using...