2.1 Embed Integration via SSO
How to setup the white label integration portal for SaaS companies with SSO
Last updated
How to setup the white label integration portal for SaaS companies with SSO
Last updated
The below steps explain how you can integrate the Embed (integration white label portal) into your own SaaS application.
In order to ensure that only your app can show the iframe and to connect your users' identity with the integrations (Flows) they might add you have to create a JWT which has to be dynamically passed. You can see a detailed setup guide below.
SSO means single sign-on. This method allows SaaS company's end customers to enable integrations using Locoia without needing to log in - the most native way possible.
SSO with a JWT claim, as per the payload-example below:
embed_user_id: id of the end-user - required
embed_user_name: name (first and last) of the end-user - optional
embed_account_id: your account id of your end-customer - required
embed_account_name: your account name of your end-customer - optional
embed_state: A string or dictionary to pass all kinds of values that you want to be accessible by the created embed flow - optional
client_authentication: A dictionary with the connector auth details for the proprietary connector specified in the embed. You can find more details here - optional
exp: expiry time stamp in epoch seconds - required
iat: issued timestamp in epoch seconds - required
Here are code examples in Python and node.js to convert the payload with JWT and a secret to the jwtToken. You can find a secret in Embed details.
Similar examples can be found for other languages.
In Embed details you can also find the iframe code. Here you only need to replace the jwtToken with the token - as per the above creation example.