Fixed some URIs in the chapter Docker Registry Configuration and Token Exchange
This commit is contained in:
parent
216bc77085
commit
7e2e485e09
2 changed files with 5 additions and 5 deletions
|
@ -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.
|
||||
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue