[KEYCLOAK-7446] - Fixing tests for authorization services documentation (#386)
This commit is contained in:
parent
4d8727ed22
commit
246c6357d1
2 changed files with 18 additions and 2 deletions
|
@ -26,7 +26,7 @@ permissions your client can use as bearer tokens to access the protected resourc
|
|||
|
||||
== Handling Authorization Responses from a UMA-Protected Resource Server
|
||||
|
||||
If a resource server is protected by a policy enforcer, it responds to client requests based on the permissions carried along with a <<_enforcer_bearer, bearer token>>.
|
||||
If a resource server is protected by a policy enforcer, it responds to client requests based on the permissions carried along with a bearer token.
|
||||
Typically, when you try to access a resource server with a bearer token that is lacking permissions to access a protected resource, the resource server
|
||||
responds with a *401* status code and a `WWW-Authenticate` header.
|
||||
|
||||
|
|
|
@ -2,3 +2,19 @@ realm-name
|
|||
0
|
||||
1
|
||||
id
|
||||
request.parameter['a']
|
||||
request.header['b']
|
||||
request.cookie['c']
|
||||
request.remoteAddr
|
||||
request.method
|
||||
request.uri
|
||||
request.relativePath
|
||||
request.secure
|
||||
request.body['/a/b/c']
|
||||
request.body['/d/1']
|
||||
request.body
|
||||
keycloak.access_token['/custom_claim/0']
|
||||
keycloak.access_token
|
||||
keycloak.access_token['/sub']
|
||||
keycloak.access_token['/preferred_username']
|
||||
keycloak.access_token['/custom_claim']
|
Loading…
Reference in a new issue