Setting up SAML2 integration is a multi-step process that involves effort from both the customer’s and MeetingPulse’s engineering teams. It consists in working with the Identity Provider (IdP) that the customer handles and authorizing this provider in MeetingPulse, which acts as a Service Provider (SP).
Setting up your SAML2 SSO
Prerequisites
A third-party Identity provider (OKTA, Azure, etc.)
A tenant created in the identity provider environment
Set-up
Use our manifest (https://app.meet.ps/api/auth/saml2 ) to set up support for our SP at your side.
Sets up the integration using the UI specific to your Identity Provider. Steps will vary depending on the third party; below is an example of an Azure setup.
Once the setup is completed on your end, please provide a link to your IdP manifest.
We will then white-list your integration to finalize the SAML Integration on our end.
Testing
You should be able to see MeetingPulse in your list of apps in your SAML portal.
Alternatively, you can test the integration by visiting the login link:
https://app.meet.ps/api/auth/saml2/login/<customer-alias>
* customer alias will be provided by us
Example - SAML2 SSO with MS Azure
Prerequisites
A Microsoft Azure account
A tenant created in the Azure environment
Access to Azure Active Directory
Set-up
Login to your Azure account as an Admin; verify that you have your correct tenant.
...