OKTA
SSO and SCIM for OKTA
Notes:
This setup needs to be implemented by an OKTA ADMIN
The SCIM integration is associated to a unique Stacksync workspace. If you have multiple workspaces (such as dev, stage and prod) you will need to set up an SCIM app for each of these Stacksync workspaces. Each workspace has independent RBAC enforcement.
SSO (SAML) setup instructions
On your OKTA homepage go on the admin section

In the Applications section, create an App integration of type SAML 2.0


Give the App name to
Stacksyncand you can add the Stacksync app logo (download file below)
Configure your SAML settings with:
Single sign-on URL:
https://auth.stacksync.com/login/callback?connection=<sso_id_provided_by_stacksync_team_for_you>Audience URI:
urn:auth0:stacksync:<sso_id_provided_by_stacksync_team_for_you>Application username:
EmailUpdate application username on
Create and updateAttribute Statements:
name=
emailsname format=
Basicvalue=
user.email
You can skip the
Feedbacksection and clickFinishSend us at
[email protected]the following details:Identity Provider Single Sign-On URLat the top of the SAML setup instructions page.

2.SAML Signing CertificatesforSHA2
Once we have received the above informations, we will activate SSO and you're all set! 🎉
SCIM setup instructions
On the General page of the SAML app you just created, enable SCIM provisioning

Go to the Stacksync Workspace Settings page at
https://app.stacksync.comto find the informations necessary for the next steps.Find your Stacksync
workspace_idon top of the page
Generate a
workspace_api_keyat the bottom of the same page. Only the owner of the Stacksync workspace can Stacksync workspace api keys.
Go back to your SAML app on the Provisionning page. Fill in the following parameter:
Base URL:
https://api.stacksync.com/v1/workspaces/<your_stacksync_workspace_id>/scim/v2/API Token:
Bearer <your_stacksync_workspace_api_key>
Allow your SCIM app to create, update and deactivate users. Stacksync users never use passwords to connect to Stacksync therefore the
Sync Passwordfeature should be disabled.
Go to the Profile Editor and add a new Attribute a new
rolesto the app. This is a standard SCIM attribute with the following fields:Data type:
string arrayDisplay name:
rolesVariables name:
rolesExternal name:
rolesExternal namespace:
urn:ietf:params:scim:schemas:core:2.0:UserDescription:
SCIM role attribute for Stacksync appEnum:
trueAttribute member:
viewerandeditorAttribute required:
trueAttribute type:
GroupGroup Priority: Use
Group Priority
Go to Directory/Groups, create 2 groups:
Stacksync EditorsandStacksync Viewers. Each group will be assigned a different role in Stacksync (editorandviewer)
Assign to the Stacksync Groups you just created the people you want to give access to Stacksync

Go back to your application and under
Assignmentsassign these 2 groups to the application. Make sure you select the right role for each group. You can ignore the other fields, Stacksync is not reading them.
That's it! 🎉
Last updated