libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

KEYCLOAK-6353 Tests broken in documentation due the invalid redirect

Browse source
This commit is contained in:
mposolda 2018-01-24 12:40:31 +01:00 committed by Marek Posolda
parent a9e5402ae1
commit d6db1b151f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
securing_apps/topics/token-exchange/token-exchange.adoc
View file

@ -17,7 +17,7 @@ to impersonate a user. Here's a short summary of the current capabilities of {p
* A client can exchange an external token for a {project_name} token.
* A client can impersonate a user
Token exchange in {project_name} is a very loose implementation of the link:http://www.ietf.org/id/draft-ietf-oauth-token-exchange-10.txt[OAuth Token Exchange] specification at the IETF.
Token exchange in {project_name} is a very loose implementation of the link:https://www.ietf.org/id/draft-ietf-oauth-token-exchange-11.txt[OAuth Token Exchange] specification at the IETF.
We have extended it a little, ignored some of it, and loosely interpreted other parts of the specification. It is
a simple grant type invocation on a realm's OpenID Connect token endpoint.
@ -72,7 +72,7 @@ NOTE: We currently only support OpenID Connect and OAuth exchanges. Support f
A successful response from an exchange invocation will return the HTTP 200 response code with a content type that
depends on the `requested-token-type` and `requested_issuer` the client asks for. OAuth requested token types will return
a JSON document as described in the link:http://www.ietf.org/id/draft-ietf-oauth-token-exchange-10.txt[OAuth Token Exchange] specification.
a JSON document as described in the link:https://www.ietf.org/id/draft-ietf-oauth-token-exchange-11.txt[OAuth Token Exchange] specification.
----
{