From a5b0bde6b93c4279c6a3362412ed028eb1cab62e Mon Sep 17 00:00:00 2001 From: nkechi Date: Sun, 27 Jan 2019 13:38:10 -0500 Subject: [PATCH 1/2] Update README.md --- docker-compose/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-compose/README.md b/docker-compose/README.md index a74b771..1c82868 100644 --- a/docker-compose/README.md +++ b/docker-compose/README.md @@ -23,7 +23,7 @@ scim-setup.sh Bearer token: jafewnqrrupcnoiqj0829fe209fnsoudbf02efsdo ``` -1. Once your scimsession file has been created, use the Linux Bash `build.sh` script to deploy the SCIM bridge. Have the domain name indicated by the DNS record created for the SCIM bridge ready. This script will do the following : +3. Once your scimsession file has been created, use the Linux Bash `build.sh` script to deploy the SCIM bridge. Have the domain name indicated by the DNS record created for the SCIM bridge ready. This script will do the following : 1. For `docker-compose`, it generate a `scim.env` file that allows the scimsession file to be passed into the container without insecurely writing it to the container filesystem. For `docker-swarm`, it will create a secret called `scimsession`, which the op-scim container will then read from `/run/secrets`, as defined in docker-compose.yml. @@ -39,4 +39,4 @@ In order to automatically launch the 1Password SCIM bridge upon startup when usi 1. Install the service file for op-scim. A [sample](op-scim.service) is provided and you'll need to change the path. 2. Reload systemd: `systemctl daemon-reload` -3. Enable the op-scim service: `systemctl enable op-scim` \ No newline at end of file +3. Enable the op-scim service: `systemctl enable op-scim` From ee1ff72c1a34418081f52a33d612aff4109f1449 Mon Sep 17 00:00:00 2001 From: nkechi Date: Sun, 27 Jan 2019 13:38:58 -0500 Subject: [PATCH 2/2] Update README.md --- docker-swarm/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-swarm/README.md b/docker-swarm/README.md index 5b3018f..c78b1a3 100644 --- a/docker-swarm/README.md +++ b/docker-swarm/README.md @@ -23,7 +23,7 @@ scim-setup.sh Bearer token: jafewnqrrupcnoiqj0829fe209fnsoudbf02efsdo ``` -1. Once your scimsession file has been created, use the Linux Bash `build.sh` script to deploy the SCIM bridge. Have the domain name indicated by the DNS record created for the SCIM bridge ready. This script will do the following : +3. Once your scimsession file has been created, use the Linux Bash `build.sh` script to deploy the SCIM bridge. Have the domain name indicated by the DNS record created for the SCIM bridge ready. This script will do the following : 1. For `docker-compose`, it generate a `scim.env` file that allows the scimsession file to be passed into the container without insecurely writing it to the container filesystem. For `docker-swarm`, it will create a secret called `scimsession`, which the op-scim container will then read from `/run/secrets`, as defined in docker-compose.yml. @@ -31,4 +31,4 @@ Bearer token: jafewnqrrupcnoiqj0829fe209fnsoudbf02efsdo 1. Lastly, it will create a container from the `1password/scim` image. A redis container will also be started automatically to be used by the SCIM bridge. -_After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine. \ No newline at end of file +_After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine.