Use Single Sign-On (SSO) for Foleon to make logging in easy and secure for your team — by allowing you to restrict access to a specific set of people. This article shows you how to set up Single Sign-On (SSO) for the Foleon platform.
⚠️ Important — Foleon only supports SSO through SAML2.0 (Security Assertion Markup Language). You or someone from your company need to have the required knowledge of integrating SSO through SAML. Without the know-how, we can not guarantee a successful implementation. For a detailed overview of the technical setup, visit developers.foleon.com for developer documentation.
💡 Foleon only offers SSO for select plans. If you're interested in using this functionality, please reach out to our Customer Success Management team.
In this article
What is SSO?
Single Sign-on, or SSO, is an authentication process that allows a user to access multiple websites or applications with one set of login credentials. This means that once you’ve logged in with your username and password, you don’t have to log in repeatedly for every single application linked to the system. You can look at it as if you have one key that unlocks multiple locks.
💡 For more information on how SSO works with Foleon, we recommend reading our article All about Single Sign-On (SSO).
How to set up SSO for the Foleon platform
In the dashboard, go to account and then click on SSO for Foleon platform. To create a new SSO configuration, click on the blue New SAML configuration button to get started.
Copy the service provider details to the SSO configuration of your identity provider.
You then enter your identity provider URL — manually type the URL or upload an XML file.
💡 We recommend entering the URL over uploading the XML file, as it will automatically update.
Next, copy the three claims to later add them to the configuration of your identity provider.
Click Save. Your new configuration will then appear in the configuration overview.
To finish your setup, add the information you copied earlier into your access management tool.
You're able to edit or delete your SSO configuration by clicking on the icons on the right side of the screen.
FAQ
-
Once we enable SSO, what happens to the currently active native users in our account?
These user accounts remain available. However, they do need to be removed once everybody has their SSO user set up — since both native and SSO users count towards the total user count.
- If SSO has been enabled for the Foleon platform, is it still possible to create non-SSO users?
Yes, this is possible — remember, they will count toward the total user count. The same applies to when you're using workspaces. -
If we enable SSO, is there any impact on the projects that currently active native users have set up?
No, there's no impact.
-
Is a user migration or mapping required before enabling SSO?
No, unless you need people to be forced into a specific workspace.
-
Are there any permissions-related changes we need to make before we enable SSO?
No, we don't believe there are any.