MoveInSync Single Sign-On (SSO)

Scope:

This document serves as a guide for administrators to configure Single Sign-On (SSO) for the MoveInSync application and download the required Federation Metadata file

An authentication method that enables users to securely authenticate with Moveinsync ETS web applications by using just one set of credentials. SSO integration also requires a set of items to be exchanged by both parties, namely Service Provider (SP) & Identity Provider (IDP) for set-up, It also details the SSO workflow overview. 

Objectives:

1. To enable seamless authentication for users accessing the Moveinsync Single Sign-On functionality

2. To ensure secure access to Moveinsync while reducing the need for multiple login credentials.

Process & Details to be Exchanged b/w Client & MoveInSync team:

Moveinsync Single Sign-On for Production:

What software (OpenSAML/Ping Identity/ADFS/ Okta )?

• MoveInSync ETS application supports SSO OpenSAML 2.0 with POST SAML profile and can be integrated with any Identity Provider (IDP) that uses this protocol for communication.

Prerequisites for SSO enablement :

ETS version should greater than 24.12.23

What does Moveinsync provide to the client?

1. For Production Sites

2. For Production based-UAT & testing sites / POC sites. 

3. For UAT sites ( based on the UAT environment )

What details does Moveinsync expect from the client?

1. IDP metadata: file/link to download the file.

2. UserName Type: which they use for SSO.

Email ID

Employee ID

3. Test Users Profiles: A user with a profile available in the moveinsync ETS application for confirming us that the SSO login is happening successfully or not.

4. SSO_SHA256: to be Enabled / Not.

SSO Flow Diagram:

Reach out/Drop mail to [email protected]