Page 1 of 1

SSO/SAML configuration for Siteline

Siteline supports Single Sign On via a SAML Identity Provider. We provide instructions for Microsoft Entra ID (formerly Azure AD) and Okta, but these instructions should apply to any SAML identity provider. Note that we need a couple days to test and deploy the authentication flow.
At a high level, we need two SAML apps (Siteline Prod and Siteline Staging) as well as a test account which can be removed once testing is done.

Microsoft Entra ID

To create an enterprise application on for Microsoft Entra ID (which you'll need to do twice), please follow the "Enable single sign-on" section in this article.

Okta

To create applications for Okta, please follow the "Create an integration" section in this article.

Your email address

SAML provider type

Domain for which to enable SSO

Test User

Please create a test account in your Azure directory. You’ll be able to remove the test account once we confirm that things work properly.
Please use the following values for the new account:
- Email address:
- Password: S1t3L1n3T3st!

Confirm email address of the test user

Siteline Prod

Create a new application for our production environment. Use the following values:
Application Name: Siteline Prod Identifier (Entity ID): https://app.siteline.com Reply URL (Assertion Customer Service URL): https://siteline-prod.firebaseapp.com/__/auth/handler

Microsoft Entra ID identifier (Prod)

Example: https://sts.windows.net/<id>

Login URL (Prod)

Example: https://login.microsoftonline.com/<id>/saml2

SAML Signing Certificate (Base64, Prod)

Siteline Staging

Create a new application for our staging environment. Use the following values:
Application Name: Siteline Staging Identifier (Entity ID): https://staging.app.siteline.com Reply URL (Assertion Customer Service URL): https://siteline-staging.firebaseapp.com/__/auth/handler

Microsoft Entra ID identifier (Staging)

Example: https://sts.windows.net/<id>

Login URL (Staging)

Example: https://login.microsoftonline.com/<id>/saml2

SAML Signing Certificate (Base64, Staging)

What to expect

We'll first use the test account to validate the authentication flow in our staging environment. If everything goes well, we'll deploy the flow to our production environment. We expect the change to take 1-2 days. We'll be in touch once the changes are deployed.
Please note that users that are already logged in will not be logged out automatically. Users that attempt to sign in with an email address belonging to your domain will be forced into the SSO flow.