With the implementation of
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | ba6fb084-9827-3160-8067-8ac7470f78b2 |
|---|
| key | PLFM-4585 |
|---|
|
synapse can now act as an OAuth 2.0 Provider. In order for application clients (See roles in
https://tools.ietf.org/html/rfc6749#section-1.1) to use Synapse as a resource server our implementation of the authorization server requires the client application to be registered before issuing authorization codes and access tokens.
...
Field | Type | Description |
|---|
cliendId | long | The id of the client |
code | string | The code for the domain validation for any of the registred redirect uris |
User
...
Interaction
There are three main actors involved in the verification
...
