OAuth Admin

As you know, we have eight microservices in the light-oauth2, and they are all responsible for different things.

Services like code, token and key will be accessed from the microservices to obtain authorization code, JWT token and public key certificate.

Others like client, service and refresh-token are used for OAuth administrators to register clients, services and manipulate refresh tokens. Until now, most users are using curl or postman to access these services through the REST API, which is very difficult to use.

It has been our priority to add the OAuth 2.0 admin to the light-portal UI and deploy the light-oauth2 services to the cloud so that developers can leverage it without starting light-oauth2 services locally.

There are three functions on the portal UI to complete the following tasks.

Client Registration [Service Registration][] [Refresh Token Admin][] [Create Test Token][]

Client Management

To access any service from a client, you need to have a valid JWT token that contains a scope that matches one of the scopes defined in the service specification for the endpoint. Typically, the original client should be a single page application or a mobile application. However, in a microservices deployment, there will be service to service invocation, and the caller will be the client of the service provider. Read More »