Single Sign-On (SSO) Set Up

This article covers how to enable single sign-on on your account, as well as the user sign-in experience once it has been enabled.

We currently support SSO integration with SAML - once this is set up, you will get an organisational code used for SSO login.
 
Jump straight to:
 

Set Up 

  1. After receiving your SSO set up request, we will send you a Reply URL and your Entity ID
  2. You will then need to follow the steps outlined below and send to us your:
    1. Certificate(Base64) file or extracted code 
    2. Login/SSO URL
    3. Provider Entity Id (Azure - Entra ID)
 
Normally, you can set this up within your SSO Provider, below is a video walkthrough of what this looks like within Azure. 
 
Video Walkthrough 
 
 
3. Once we have received the above and set up your integration, you may have an option in your SSO provider to test the connection. In Azure, you can do this by adding yourself as a user (to do this, navigate to Users and Groups > Add user/group).
If the test is successful, you will see a green tick and message confirming that the Entra ID has successfully issued a token to the application. This is also covered in the video above.
 
4. We will now send you your Organisation Code. 
 

If your institution does not use Azure and these instructions do not match your SSO provider's system, please reach out to support@bodyswaps.co and we will support you with this process. 

Signing in with SSO

 
After setting up SSO on your account, ALL users must sign in with the SSO SIGN IN button (next to LET'S GO!), instead of the Username and Password option. 
Bodyswaps Go sign-in screen with Email, Password fields, and SSO Sign In link.
 
The user will be prompted to enter your Organisation Code, and this would then trigger the SSO sign in process.
Screen capture of the SSO Sign in page asking for Organisation Code and options to cancel or sign in.
A pop-up will then appear with your institution's sign in page and the user can enter their details to access Bodyswaps Go. 


Please note that you will need to communicate your Organisation Code to your Bodyswaps users. 

 
If a user on an account with SSO enabled attempts to sign in with their Username and Password instead of SSO, they will received the below error message. 
 
Screen capture showing an error message stating "You must log in via SSO."

 

When you add new users to the account, they'll receive this email instead of the standard password setting invite: 

Email screen capture for creating a Bodyswaps profile with SSO enabled.