How to Connect Okta Identity Provider to ChannelMix

Prerequisite

We need to be able to apply a routing rule to your organization. Typically this can be done via an email domain, for instance for InMarket we could send any user with the domain @inmarket.com to InMarket's SSO

Instructions

1. Inside of the Okta Admin Dashboard, navigate to Applications and select Create App Integration
2. Select OIDC - OpenID Connect for the Sign-in method and Web Application for the Application type
3. On the next screen, the App integration name can be anything you would like, but something like “ChannelMix IdP Integration” or “ChannelMix OIDC Connection” can be helpful in remembering what this app is used for.
4. Keep Grant type default with “Authorization Code”
5. For the Sign-in redirect URI enter “https://sso.channelmix.com/oauth2/v1/authorize/callback”
6. For Sign-out redirect URIs enter any location you'd like to send your users to after they log out. Our default redirect is "https://app.channelmix.com/user-logged-out" which you can use as well
7. Leave Base URIs blank
8. Select the desired Controlled access level for your users. By default, we have selected "allow anyone in our organization to access" though you could limit this to certain groups for more fine grained control.
   1. If you have selected “Allow everyone in your organization to access” you are given the option to immediately grant access to users on their first login so you don’t have to provision them beforehand. Or you could provision these users before they are allowed to use your app.
   2. If you selected “Limit access to selected groups” you will be asked to select the group(s) you want to limit access to

9. Your application is complete! On the next screen you will need to copy the Client ID and Secret and send it to ChannelMix. ChannelMix will also need your Okta Instance URL so it can be configured in ChannelMix's identity provider. For example, this is ChannelMix's URL: https://sso.channelmix.com)

Items to Send to ChannelMix

These can be shared via a shared password in C3.

1. Application Client ID
2. Application Secret
3. Okta Instance URL