Overview
We support both an SP initiated and IdP initiated SAML SSO flow. In the context of these flows the following definitions apply:
Identity Provider (IdP): Yapster
Service Provider (SP): the partner application to which the user has requested access.
The IdP flow must be supported by the Service Provider to ensure that users are able to login directly from the Yapplications tab within Yapster.
An SP initiated flow is optional and only required if the Service Provider wishes to support authentication of users associated with Yapster accounts arriving directly to their web site or application.
Yapster Will Provide
A copy of the certificate and public key used for signing our SAML Responses and Assertions. This will be provided over a secure channel (e.g. https://keybase.io)
Our IdP Entity ID value
Service Provider Will Provide
ACS URL.
Expected Entity ID (Audience URI) value.
Name ID mapping details (e.g. map to payroll ID, email, etc.)
Required Attribute Statements (names and expected value mappings.)
Sandbox environmentâwith admin user accessâwith which Yapster can test and verify integration.
Endpoints
The endpoints are standard SAML endpoints. In order to use them, you will need a workspace configured (and the org-id indentifier for the accompanying organisation).
NB: Depending on your browser, you might need to scroll down after clicking the link below.