Skip to content

Latest commit

 

History

History
73 lines (38 loc) · 3.43 KB

CONFIGURE_GOOGLE_SOURCE.md

File metadata and controls

73 lines (38 loc) · 3.43 KB

Configure Google IdP

To use Google Directory as an IdP, you must perform the following steps:

  1. Go to Google Cloud Console and select your project

img1

  1. Go to "IAM & Admin" -> "Service Accounts"

img2

  1. Click on the button "Create Service Account" and create your Service Account

img3

  1. Click on the created Service Account

img4

  1. Then click on the "Keys" tab

img5

  1. Click on "Add Key" and select "Create new key"

img6

  1. Select "JSON" and create the key (then it will download your Service Account Key - you'll use this key to authenticate in the application)

img7

  1. Go back to the "Details" tab and copy your "Unique ID"

img8

  1. Go to the Google Admin Console and go to "Security" -> "Access and data Control" -> "API Controls"

img9

  1. Click on "MANAGE DOMAIN WIDE DELEGATION"

img10

  1. Click on "Add new" to add a new API Client

img11

  1. Then fill the form with the Service Account Unique ID that you copied and the OAuth Scope "https://www.googleapis.com/auth/admin.directory.user"

img12

And your Service Account is configured. Now you need to set the following environment variables:

  • SDM_SCIM_IDP_GOOGLE_KEY_PATH - the path of the service account key file
  • SDM_SCIM_IDP_GOOGLE_SUBJECT_USER - the service account admin email

An user can only be assigned to one OrgUnit at a time

Additional flags

To add a filter to the IdP search, you can use the -idp-query flag refering to the Google Users Search Documentation

Additional env variables

  • SDM_SCIM_IDP_GOOGLE_ROOT_ORG_UNIT_ALIAS - alias for representing the root organization unit in strongDM roles

Running with Docker

To configure the Google IdP on Docker you need to follow these steps:

  • Go to docker-compose.yml and in the scim-integrations service refer your service account key file in the volume source (/path/to/your/idp-key.json:/scim-integrations/keys/idp-key.json) and leave the destination path as it is, or else it won't work.
  • Refer to the overall steps of how to run SCIM Integrations with Docker.