updates to server admin guide
This commit is contained in:
parent
875f70e23e
commit
9431096112
2 changed files with 9 additions and 9 deletions
|
@ -11,7 +11,7 @@ For more information on how to set up and configure a Docker registry, see the l
|
||||||
|
|
||||||
=== Docker Registry Configuration File Installation
|
=== Docker Registry Configuration File Installation
|
||||||
|
|
||||||
For users with more advanced docker registry configurations, it is generally recommended to provide your own registry configuration file. The {project_name} docker provider supports this mechanism via the _Registry Config File_ Format Option. Choosing this option will generate output similar to the following:
|
For users with more advanced Docker registry configurations, it is generally recommended to provide your own registry configuration file. The {project_name} Docker provider supports this mechanism via the _Registry Config File_ Format Option. Choosing this option will generate output similar to the following:
|
||||||
|
|
||||||
auth:
|
auth:
|
||||||
token:
|
token:
|
||||||
|
@ -37,18 +37,18 @@ WARNING: Don't forget to configure the `REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE` over
|
||||||
|
|
||||||
=== Docker Compose YAML File
|
=== Docker Compose YAML File
|
||||||
|
|
||||||
WARNING: This installation method is meant to be an easy way to get a docker registry authenticating against a keycloak server. It is intended for development purposes only and should never be used in a production or production-like environment.
|
WARNING: This installation method is meant to be an easy way to get a docker registry authenticating against a {project_name} server. It is intended for development purposes only and should never be used in a production or production-like environment.
|
||||||
|
|
||||||
The zip file installation mechanism provides a quickstart for developers who want to understand how the keycloak server can interact with the docker registry. In order to configure:
|
The zip file installation mechanism provides a quickstart for developers who want to understand how the {project_name} server can interact with the Docker registry. In order to configure:
|
||||||
|
|
||||||
1. From the desired realm, create a client configuration. At this point you won't have a docker registry - the quickstart will take care of that part.
|
1. From the desired realm, create a client configuration. At this point you won't have a Docker registry - the quickstart will take care of that part.
|
||||||
2. Choose the "Docker Compose YAML" option from the installation tab and download the .zip file
|
2. Choose the "Docker Compose YAML" option from the installation tab and download the .zip file
|
||||||
3. Unzip the archive to the desired location, and open the directory.
|
3. Unzip the archive to the desired location, and open the directory.
|
||||||
4. Start the docker registry with `docker-compose up`
|
4. Start the Docker registry with `docker-compose up`
|
||||||
|
|
||||||
INFO: it is recommended that you configure the docker registry client in a realm other than 'master', since the HTTP Basic auth flow will not present forms.
|
NOTE: it is recommended that you configure the Docker registry client in a realm other than 'master', since the HTTP Basic auth flow will not present forms.
|
||||||
|
|
||||||
Once the above configuration has taken place, and the keycloak server and docker registry are running, docker authentication should be successful:
|
Once the above configuration has taken place, and the keycloak server and Docker registry are running, docker authentication should be successful:
|
||||||
|
|
||||||
[user ~]# docker login localhost:5000 -u $username
|
[user ~]# docker login localhost:5000 -u $username
|
||||||
Password: *******
|
Password: *******
|
||||||
|
|
|
@ -22,7 +22,7 @@ $ sudo subscription-manager repos --enable=jb-eap-7-for-rhel-<RHEL_VERSION>-serv
|
||||||
Install the EAP 7 adapters for OIDC using the following command:
|
Install the EAP 7 adapters for OIDC using the following command:
|
||||||
|
|
||||||
----
|
----
|
||||||
$ sudo yum install eap7-keycloak-adapter-sso7_2
|
$ sudo yum install eap7-keycloak-adapter-sso7_3
|
||||||
----
|
----
|
||||||
|
|
||||||
NOTE: The default EAP_HOME path for the RPM installation is /opt/rh/eap7/root/usr/share/wildfly.
|
NOTE: The default EAP_HOME path for the RPM installation is /opt/rh/eap7/root/usr/share/wildfly.
|
||||||
|
@ -59,7 +59,7 @@ $ sudo subscription-manager repos --enable=jb-eap-6-for-rhel-<RHEL_VERSION>-serv
|
||||||
Install the EAP 6 adapters for OIDC using the following command:
|
Install the EAP 6 adapters for OIDC using the following command:
|
||||||
|
|
||||||
----
|
----
|
||||||
$ sudo yum install keycloak-adapter-sso7_2-eap6
|
$ sudo yum install keycloak-adapter-sso7_3-eap6
|
||||||
----
|
----
|
||||||
|
|
||||||
NOTE: The default EAP_HOME path for the RPM installation is /opt/rh/eap6/root/usr/share/wildfly.
|
NOTE: The default EAP_HOME path for the RPM installation is /opt/rh/eap6/root/usr/share/wildfly.
|
||||||
|
|
Loading…
Reference in a new issue