With SSO (Single Sign-On), users in your organization can easily authenticate using accounts they already have within Okta.
Prerequisites
To have SSO enabled for your organization a team or an enterprise plan is required (see pricing). Once in place, you can access your team account via Billing Team tab (available in Settings, alternatively using this link: https://sellercrowd.com/settings/billing-team/) where you can get following details:
Supported features
IdP-initiated SSO
SP-initiated SSO
Just-In-Time provisioning
Configuration steps
1. Look up "SellerCrowd" in Okta's application directory. And click it to navigate to SellerCrowd application page.
3. Click "Add Integration" button. You'll be taken to the "General settings" page where you can define your own (internal) name for this integration ("SellerCrowd" by default). Adjust as you see fit and click "Done".
4. The integration is now installed, but you need to fill in "Organization ID" variable. To do that, navigate to the "Sign On" tab and click "Edit" link.
5. Scroll down to the "Advanced Sign-on Settings" section and find the "Organisation ID" input. Fill it in with Organisation Id value, available at Sellercrowd's Billing Team page (see Prerequisites)
6. From the "Sign On" tab, copy the Metadata URL from the Okta Admin Console, SAML 2.0 Sign on methods section.
7. Open "Billing Team" page in Sellercrowd (see Prerequisites) and click "I have the XML".
8. Open in browser copied url (obtained in step 6), copy its content and paste to form:
โ
9. Click "Enable SSO". You can start assigning people to the application on the Okta side (to allow all or some of your users to actually have access to SellerCrowd).
Notes
The following SAML attributes are supported:
name (Okta side) | value (mapped to) | update on login |
givenName | user.firstName | yes* |
familyName | user.lastName | yes* |
*) It can be disabled, please send request to support (email: techsupport@sellercrowd.com).
SP-initiated SSO
Enter your email, then click Continue.