Collections of the oauth category
Overview
Used in the OAuth 2.0 and OpenId Connect 1.0 authorization/identification process (Authorization Code Grant mechanism).
Served by the ws microservice.
The three-stage process of external OAuth 2.0 authorization and OpenId Connect 1.0 identification followed by linking to a local user account in one of the system local domains assumes:
-
registration of the system with an external OAuth authorization provider;
-
a configured and enabled OAuth authorization provider (an 'oauth/Providers' collection entity);
-
a token authorization script configured and registered in the master domain ('iam_token_svcscript_code').
In the root client web application, alternative external authorization buttons are displayed for all enabled OAuth authorization providers listed in the 'oauth/Providers' collection.
When such a button is pressed, according to the OAuth 2.0 and OpenId Connect 1.0 protocol, a chain of successive redirects between the system and the external authorization server is performed. The further process corresponds to the OAuth protocol and broadly looks like this:
-
LOCAL: '/oauth/redirect/<KEY>' - searches for the provider, creates an authorization request, redirects to the external authorization server.
-
EXT: '/authorize' - the external authorization service gives the user the opportunity to enter their credentials and allow access from the communication system.
-
LOCAL: '/oauth/receiver' - reverse redirect handler, receives the code, exchanges it for a token, receives credentials from the external data server.
-
LOCAL: '/oauth/enter' - executes the script linking the identifier of the request authorized on the external server with the local user account, creates a session.
-
LOCAL: '/app-root' - opens in the authorized state and displays the list of available applications to the user.
Endpoints
-
oauth/Providers - OAuth authorization providers.
-
oauth/Requests - OAuth authorization requests.