oauth/Requests
Collection of OAuth 2.0 authorization and OpenId Connect 1.0 identification providers.
Used for the three-stage external authorization process and linking an external account to a local account.
Successful completion requires a token authorization service script configured in the master domain ('iam_token_svcscript_code').
Contained only in the master domain.
Storage type: runtime.
| Field | Description |
|---|---|
|
Identifier |
|
Request initiator IP address. |
|
Request state:
Correct state sequence: 'initial' → 'authorized' → 'linked'. |
|
Occurred error text. Populated when the 'error' status is set. |
|
OAuth authorization provider key (from the 'oauth/Providers' collection). |
|
OAuth authorization provider identifier (from the 'oauth/Providers' collection). |
|
Token for refreshing the 'access_token' value used to access the external data server. After initial authorization completes, the system does not access the external authorization server or data server, so the entity is deleted automatically. |
|
Scope granted during external authorization. May be smaller than registered for the system if optional_scope is used and the user does not select some sections. |
|
Discovered identifier of the user external account on the external authorization server. |
|
Discovered login of the user external account on the external authorization server. May be used for matching when linking to a local user account. |
|
Discovered name of the user external account on the external authorization server. May be used when creating a local user account. |
|
Discovered email of the user external account on the external authorization server. May be used both when creating a local user account and when linking to an existing user account. |
|
Local system domain where linking to the user external account is proposed. |
|
Collected user information in the external system for placement in the 'opts.info' field of the matched account. |
|
Original content about the user external account. Determined by parsing JWT content or JSON content in the external data server response or the redirect from the external authorization server. |
|
Request creation/modification timestamp. |
|
Request lifetime in seconds. Counted from each entity modification (the 'ts' field sets the timestamp). After expiry the request is deleted automatically. In 'initial' and 'authorized' states the lifetime is 120 seconds. In 'ready' state - 60 seconds. After initial authorization completes, the system does not access the external authorization server or data server, so the entity is deleted automatically. |