Testing For Cloud Provider Login
Please perform the following steps to determine if you are in case #1 vs. #2 above:
- Browse to https://salescookie.com
- Click on Login in the top right corner
- Click on the appropriate button
If this method works, then you do NOT have custom SSO. The less expensive Sales Cookie Business plan is sufficient.
Optionally, you can restrict logins to one SSO provider only, so that logins via a user name / password, or other SSO providers, are disabled:
- Login to your workspace
- Click on Settings > Security > Manage Settings on the left navigation bar
- Enter values in this field

- Common values include
- "salesforce" for SalesForce
- "quickbooks-online" for QuickBooks
- "google" for Google
- "windowslive" for Microsoft
- "xero" for Xero
- Additional settings on this page make it also possible to restrict access to certain IPs or domain names
At this time, everything is ready. Your users will be able to login via your SSO provider (with the option to limit logins to this SSO provider only).
If this method does NOT work, you are using custom SSO for your domain:
- The more expensive Sales Cookie Business+ plan is required
- Special configuration steps are required (please see below)
Configuring Custom SSO
Special steps are required to enable custom SSO. Those steps need to be performed by you and us (Sales Cookie) to establish trust. Custom SSO is typically required when you have customized your authentication, and the general SSO authentication provided by Google, Microsoft, etc. do not work.
Depending on the platform you are using, typical configuration steps may include:
- Registering an application in your tenant (ex: creating an Azure AD application)
- Setting up SAML records in your tenant
- Downloading X509 certificate / OAuth secrets
- Entering authorized login URLs within your tenant (ex:
https://salescookie.auth0.com/login/callback
)
The method used to configure SSO varies greatly from provider to provider, but will require manual intervention. On our end, Sales Cookie uses Auth0 for all authentication. Auth0 is part of the Okta product family. Here are a few examples of what steps may look like - both on your end, and our end (Auth0):
- If you use Google Workspace - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/google-apps
- If you use Microsoft Azure AD - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/azure-active-directory/v2
- If you use Okta - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/okta
- If you support SAML - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/saml
- If you support PingFederate - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/ping-federate
- Etc. - https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers
Because of the complexity of setting up custom authentication, we require the more expensive Sales Cookie Business+ plan. Besides the cost of configuration, this helps us cover the cost of Auth0, whose pricing model requires additional fees for each custom SSO enterprise connection. Please reach out to support for help configuring custom SSO.