Fliplet offers secure Single Sign-On (SSO) to your apps through the SAML2 standard. Setting it up usually requires IT/backend support from your administrators for the initial configuration phase only.

How does it work?

Create a new Fliplet app or use your existing one, then drop the SAML2 component into your screen:

Once you’ve dropped the component into your screen, a “Sign in” button will appear along with the configuration interface on the right-hand side:

The first thing you’ll need is to press the copy the link to the metadata XML button on the bottom right of the screen. That will copy on your computer clipboard a URL to the metadata file which you will need to provide to your IT. Its format is the following:
Please note that the 123 will change depending on your Fliplet app ID. If your system does not allow importing the above XML, you can still configure the integration by manually getting the fields to use from the XML. These are the ones you will need and how to find them:
  1. Entity ID (or Identifier) has a unique value for each Fliplet app and has the same value as the metadata URL above. It can also be seen in the md:EntityDescriptor node under the entityID attribute of the XML.
  2. Reply URL (or Assertion URL) is also dynamic and depends on your Fliplet App ID. Here’s a sample value for it: https://api.fliplet.com/v1/session/providers/saml2/callback/1234. Its value can also be found in the md:AssertionConsumerService node of the XML under the Location attribute.
  3. Service Provider Certificate (PEM String format): Download

Note: the three fields above can also be retrieved from the metadata XML under the following paths: SingleSignOnService, SingleLogoutService, X509Certificate.

Once you have given the above to your IT, they should be able to configure the integration and come back to you with a few details which you will need to paste back on the Fliplet SAML2 component configuration interface:

  • Single sign-on login URL
  • Single sign-on logout URL
  • Your Identity Provider Certificate(s) in PEM format

Force authentication

When enabled, your Identity Provider will require the user to authenticate even if they have previously logged in on the same device and browser.

Keep the user logged in for 
Use this setting to force user re-authentication after your selected number of hours

Automatically log out the user due to inactivity after 
Use this setting to automatically log out the user after a period of inactivity in the app

This option forces the login to be done on Safari instead of using the in-app browser.

When everything is set up, clicking the sign-in button on the Fliplet app should redirect the user to your login screen. Once a login succeeds, the user will be redirected back to the Fliplet app at the screen you selected in the component configuration.

Exposing data

Your IT might ask you what data should be exposed to the Fliplet app with the integration. We usually recommend our clients expose the following properties of the user object:

  • email
  • given_name
  • surname

These can be used to enhance your Fliplet app user experience by displaying them on your app screens once the user has logged in. This is described further below in this document.

Adding more security to your app

Once the integration is all working, you can secure your app by requiring a valid SAML2 session to all screens except the login one. This only takes a few seconds via the App security tab of your app settings:


The integration flow explained

  1. The user clicks a login button on a Fliplet app and gets redirected to the client’s login page.
  2. The user logs in with his/her organization credentials (not Fliplet credentials) and gets redirected back to Fliplet servers.
  3. Fliplet servers validate the login request and redirect the user back to the Fliplet app and to the relevant page.
For more technical information please see our developer docs here: https://developers.fliplet.com/API/integrations/sso-saml2.html#getting-started

Third-party reference docs

The following links might help you and your IT to configure the integration. Please use the link depending on the backend system you use:


Was this article helpful?