sessions
This commit is contained in:
parent
4ae61940ee
commit
2374285f45
1 changed files with 1 additions and 1 deletions
|
@ -24,7 +24,7 @@ Offline tokens can also be revoked by setting a <<fake/../../sessions/revocation
|
|||
To be able to issue an offline token, users need to have the role mapping for the realm-level role `offline_access`.
|
||||
Clients also need to have that role in their scope.
|
||||
|
||||
The client can request offline token by adding the parameter `scope=offline_access` when sending authorization request to {{book.project.name}.
|
||||
The client can request offline token by adding the parameter `scope=offline_access` when sending authorization request to {{book.project.name}}.
|
||||
The {{book.project.name}} OIDC client adapter automatically adds this parameter when you use it to access secured URL of your application (ie.
|
||||
http://localhost:8080/customer-portal/secured?scope=offline_access ). The Direct Access Grant and Service Accounts also
|
||||
support offline tokens if you include `scope=offline_access` in the body of the authentication request.
|
||||
|
|
Loading…
Reference in a new issue