From 32c071a797fcb83284dbedee22d505e0fc059ef6 Mon Sep 17 00:00:00 2001 From: Duncan Stevenson-Price Date: Tue, 16 Jul 2019 15:45:21 +0100 Subject: [PATCH] Documentation edits --- aws-terraform/README.md | 5 +++-- docker/README.md | 7 ++++--- kubernetes/README.md | 5 +++-- scim-setup.sh | 8 -------- 4 files changed, 10 insertions(+), 15 deletions(-) delete mode 100755 scim-setup.sh diff --git a/aws-terraform/README.md b/aws-terraform/README.md index 8b5b9ce..c876a99 100644 --- a/aws-terraform/README.md +++ b/aws-terraform/README.md @@ -10,14 +10,15 @@ This example describes one of the simplest methods of deploying the 1Password SC ## Prepare your 1Password Account -Log in to your 1Password account [using this link](https://my.1password.com/scim/setup). It will take you to a hidden setup page for the SCIM bridge. +Log in to your 1Password account [using this link](https://start.1password.com/settings/provisioning/setup). It will take you to the setup page for the SCIM bridge. Follow the on-screen instructions which will guide you through the following steps: * Create a Provision Managers group * Create and confirm a Provision Manager user +* Generate your SCIM bridge credentials -You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will creates, confirms, and suspends users, and creates and manages access to groups. You should use an email address that is unique and not that of another user. +You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will create, confirm, and suspend users, and create and manage access to groups. You should use an email address that is unique. The bearer token and scimsession file combined can be used to sign in to your Provision Manager account. You’ll need to share the bearer token with your identity provider, but it’s important to **never share it with anyone else**. And never share your scimsession file with **anyone at all**. diff --git a/docker/README.md b/docker/README.md index afa4403..31b2291 100644 --- a/docker/README.md +++ b/docker/README.md @@ -26,14 +26,15 @@ The 1Password SCIM bridge requires SSL/TLS in order to communicate with your IdP ## 4: Prepare your 1Password Account -Log in to your 1Password account [using this link](https://my.1password.com/scim/setup). It will take you to a hidden setup page for the SCIM bridge. +Log in to your 1Password account [using this link](https://start.1password.com/settings/provisioning/setup). It will take you to the setup page for the SCIM bridge. Follow the on-screen instructions which will guide you through the following steps: * Create a Provision Managers group * Create and confirm a Provision Manager user +* Generate your SCIM bridge credentials -You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will creates, confirms, and suspends users, and creates and manages access to groups. You should use an email address that is unique and not that of another user. +You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will create, confirm, and suspend users, and create and manage access to groups. You should use an email address that is unique. The bearer token and scimsession file combined can be used to sign in to your Provision Manager account. You’ll need to share the bearer token with your identity provider, but it’s important to **never share it with anyone else**. And never share your scimsession file with **anyone at all**. @@ -49,7 +50,7 @@ You should move your newly created `scimsession` file into the `scim-examples` f 1. Ask if you want to deploy with Docker Swarm or Compose - 1. For `docker-compose`, it will 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. + 1. Add your `scimsession` to the SCIM bridge container, using a .env file for Docker Compose or a swarm secret for Docker Swarm. 1. You will be prompted for your SCIM bridge domain name which will configure LetsEncrypt to automatically issue a certificate for your bridge. diff --git a/kubernetes/README.md b/kubernetes/README.md index 3a30f40..55fa554 100644 --- a/kubernetes/README.md +++ b/kubernetes/README.md @@ -22,14 +22,15 @@ This will deploy a single redis instance listening on Kubernetes internal DNS `r ## Prepare your 1Password Account -Log in to your 1Password account [using this link](https://my.1password.com/scim/setup). It will take you to a hidden setup page for the SCIM bridge. +Log in to your 1Password account [using this link](https://start.1password.com/settings/provisioning/setup). It will take you to the setup page for the SCIM bridge. Follow the on-screen instructions which will guide you through the following steps: * Create a Provision Managers group * Create and confirm a Provision Manager user +* Generate your SCIM bridge credentials -You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will creates, confirms, and suspends users, and creates and manages access to groups. You should use an email address that is unique and not that of another user. +You can then download the `scimsession` file and save your bearer token. The `scimsession` file contains the credentials for the new Provision Manager user. This user will create, confirm, and suspend users, and create and manage access to groups. You should use an email address that is unique. The bearer token and scimsession file combined can be used to sign in to your Provision Manager account. You’ll need to share the bearer token with your identity provider, but it’s important to **never share it with anyone else**. And never share your scimsession file with **anyone at all**. diff --git a/scim-setup.sh b/scim-setup.sh deleted file mode 100755 index 6b91c41..0000000 --- a/scim-setup.sh +++ /dev/null @@ -1,8 +0,0 @@ -#!/bin/bash - -mkdir session - -docker run -it -v $PWD/session:'/op-scim/session' -v $HOME/.op:'/root/.op' 1password/scim:v0.8.4 /op-scim/create-session-docker.sh - -cp ./session/scimsession ./scimsession -rm -rf ./session \ No newline at end of file