SSO (Single Sign On) Configuration

The Messaging Hub provides Single Sign-On (SSO) functionality for enterprise customers, allowing authorised users to access the web application via a single identity without the need for separate logins and passwords. This allows IT administrators to better manage team access and keeps information more secure.

• How to configure Single Sign On (SSO) with your Identity Provider
• How to configure the Messaging Hub to use Single Sign On (SSO)
• Frequently Asked Questions (FAQs)

Before you get started...

You will need to meet certain criteria before you can configure SSO:

• An identity provider that supports the SAML 2.0 standard
  • We offer support for the following providers:
    • Microsoft Azure AD (Active Directory)
    • Okta
• Access/permissions to configure applications within your identity provider
• User credentials with admin-level access to the parent account on the Messaging Hub

Configuring your SSO Identity Provider

We use SAML 2.0 (Security Assertion Markup Language), a standard that permits Identity Providers (IdP) to safely pass authorisation credentials, such as your username and password, to service providers like our Messaging Hub.

1. The first step is to create a new SAML application with your IdP:

• For Microsoft Azure AD, follow this guide
• For Okta, follow this guide

2. Configure the application using the following settings:

For Microsoft Azure AD 

• Claim

• Additional Claim

For Okta

• Okta Attributes

3. Configure a logo (Optional)

4. Assign users or groups to the application

5. Copy or download the IdP XML metadata - you will need this for Step 5 of Configuring the Messaging Hub

Configuring the Messaging Hub

1. Log into the parent account in the Hub - remember, your user credentials will need admin-level access to proceed from here!

2. Once you're logged into the Hub, go to the menu and click on the    icon, then select Account:

3. Select the Security tab.

4. Configure the email domains that you want to enable for SSO - email domains can only be used once per account hierarchy so if you set an email domain at a sub-account level, you can't set the same email domain on another sub-account.

5. Use the dropdown arrow to select your Identity Provider (IdP) - either Okta or Azure AD - if your IdP is not listed, you can submit a support request to chat more about extending SSO support to your IdP

6. Enter the XML provided by your IdP in the field provided.

7. When someone logs into the Hub using SSO but they don't already have a user profile, you can allow the Hub to automatically create a new user with the credentials provided by the IdP. Just toggle this switch to On to enable.

8. Use the dropdown arrow to set the default user role to be assigned to these newly created profiles.

9. Select the accounts & sub-accounts you want to allow these new users to have access to.

10. Toggling this switch to On means that any users logging in with credentials matching your nominated email domains will be forced to log into the Hub using SSO only.

FAQs

• My organization uses an identity service provider (IdP) that's not in the list. Will it be supported?
  Please contact the support team via the link at the bottom of the page with the details of which identity provider you would like to use.
• Do you support on-premises Microsoft Active Directory?
  No, we only support Azure Active Directory.
• Do you support IdP initiated SSO?
  Unfortunately not at this stage. Users will need to re-enter their email address in the Log in with Single Sign On page.
• Does enforcing SAML SSO log out users?
  No, active user sessions stay logged in until they expire. The next time a user needs to log in, they will need to log in with SAML SSO.

If you have further questions, please contact support@messaging.tpgtelecom.com.au