Skip to content

Commit

Permalink
Update Google DSync envs (#397)
Browse files Browse the repository at this point in the history
* Update google dsync envs

* Add to Upgrade Guide

* Tweak
  • Loading branch information
niwsa authored Mar 12, 2024
1 parent bd56b04 commit d9dcc62
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 3 deletions.
16 changes: 13 additions & 3 deletions docs/jackson/deploy/env-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -411,8 +411,18 @@ The Google authentication client secret.

NPM library option: `dsync.providers.google.clientSecret`

### **DSYNC_GOOGLE_REDIRECT_URI**
### **dsync.providers.google.authorizePath**

The URI to redirect to after completing the authentication request.
The authorization endpoint for Google SCIM.

NPM library option: `dsync.providers.google.callbackUrl`
NPM library option: `dsync.providers.google.authorizePath`

For example: `/api/scim/oauth/authorize`

### **dsync.providers.google.callbackPath**

The path to redirect to after completing the authorization request for Google SCIM.

NPM library option: `dsync.providers.google.callbackPath`

For example: `/api/scim/oauth/callback`
8 changes: 8 additions & 0 deletions docs/jackson/upgrade.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Upgrade Guide

## Upgrading to v1.21.0

Google DSync Connections will be supported on the back of following changes related to Authorization. These will ease the process of surfacing up the OAuth endpoints for Google SCIM.

1. Removed `DSYNC_GOOGLE_REDIRECT_URI`, `GOOGLE_REDIRECT_URI` env vars for Jackson service.
2. Removed `dsync.providers.google.callbackUrl` from npm.
3. Our npm will take in new options - `dsync.providers.google.authorizePath` and `dsync.providers.google.callbackPath`. These will be used alongside `externalUrl` to construct the full path

## Upgrading to v1.14.0

We have changed the schema bit to introduce a new column called `namespace` to speed up scans. You will have to run the migration scripts if you are manually managing migrations. For example PlanetScale where auto migrations are not supported due to a difference between MySQL and PlanetScale.
Expand Down

0 comments on commit d9dcc62

Please sign in to comment.