From 7e2e485e09b55be1bc0ddf071451f6daf1b5e5ee Mon Sep 17 00:00:00 2001 From: Frieder Date: Fri, 7 Dec 2018 14:02:07 +0100 Subject: [PATCH] Fixed some URIs in the chapter Docker Registry Configuration and Token Exchange --- securing_apps/topics/docker/docker-overview.adoc | 8 ++++---- securing_apps/topics/token-exchange/token-exchange.adoc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/securing_apps/topics/docker/docker-overview.adoc b/securing_apps/topics/docker/docker-overview.adoc index b1f2ec2b32..24d2ec5278 100644 --- a/securing_apps/topics/docker/docker-overview.adoc +++ b/securing_apps/topics/docker/docker-overview.adoc @@ -15,9 +15,9 @@ For users with more advanced docker registry configurations, it is generally rec auth: token: - realm: http://localhost:8080/auth/auth/realms/master/protocol/docker-v2/auth + realm: http://localhost:8080/auth/realms/master/protocol/docker-v2/auth service: docker-test - issuer: http://localhost:8080/auth/auth/realms/master + issuer: http://localhost:8080/auth/realms/master This output can then be copied into any existing registry config file. See the link:https://docs.docker.com/registry/configuration/[registry config file specification] for more information on how the file should be set up, or start with link:https://github.com/docker/distribution/blob/master/cmd/registry/config-example.yml[a basic example]. @@ -28,9 +28,9 @@ WARNING: Don't forget to configure the `rootcertbundle` field with the location Often times it is appropriate to use a simple environment variable override for develop or POC Docker registries. While this approach is usually not recommended for production use, it can be helpful when one requires quick-and-dirty way to stand up a registry. Simply use the _Variable Override_ Format Option from the client installation tab, and an output should appear like the one below: - REGISTRY_AUTH_TOKEN_REALM: http://localhost:8080/auth/auth/realms/master/protocol/docker-v2/auth + REGISTRY_AUTH_TOKEN_REALM: http://localhost:8080/auth/realms/master/protocol/docker-v2/auth REGISTRY_AUTH_TOKEN_SERVICE: docker-test - REGISTRY_AUTH_TOKEN_ISSUER: http://localhost:8080/auth/auth/realms/master + REGISTRY_AUTH_TOKEN_ISSUER: http://localhost:8080/auth/realms/master WARNING: Don't forget to configure the `REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE` override with the location of the {project_name} realm's pulic certificate. The auth configuration will not work without this argument. diff --git a/securing_apps/topics/token-exchange/token-exchange.adoc b/securing_apps/topics/token-exchange/token-exchange.adoc index 09e2f36935..37aba88c9e 100644 --- a/securing_apps/topics/token-exchange/token-exchange.adoc +++ b/securing_apps/topics/token-exchange/token-exchange.adoc @@ -23,7 +23,7 @@ We have extended it a little, ignored some of it, and loosely interpreted other a simple grant type invocation on a realm's OpenID Connect token endpoint. ---- -/realms/{realm}/protocol/openid-connect/token +/auth/realms/{realm}/protocol/openid-connect/token ---- It accepts form parameters (`application/x-www-form-urlencoded`) as input and the output depends on the type of token you requested an exchange for.