Security Assertion Markup Language (SAML) is an XML-based framework for enabling authentication through a third party identity provider or in-house single sign-on application.
SAML comes in handy for organizations which use multiple applications or services and need a single source to manage member activity. Instead of creating multiple credentials for different applications, with SAML you can create one set of credentials per member and allow them to access multiple applications.
SAML offers the ability to:
Team Member: Team Member is an employee of the organization, say, Acme Inc, and is an authorized user of Acme Inc's Fill User Interface.
Authentication: The verification mechanism that certifies an individual is the actual person they claim to be.
IdP: Identity Provider (IdP) is the platform or application that provides authentication for the member.
SP: Service Provider (SP) is the application that needs authentication for allowing access to the member. For the entirety of this doc, Fill is the Service Provider.
Login URL: This URL will take you to the IdP's login page asking for your credentials. Login URL is provided by your IdP and must be added in Fill while integrating.
X.509 Certificate: Fill accepts only X.509 Certificate to validate the authenticity of an IdP.
You can log in to Fill using one of the ways listed below:
You can add Fill app in Okta using the steps below:
These are required and need to be pasted in your Fill User Interface while enabling SAML.
You can add Fill app in Google using the steps below:
These are required and need to be pasted in your Fill User Interface while enabling SAML.
You can add Fill app in Microsoft's Azure Active Directory using the steps below:
To disable SAML, go to Settings > Team & SSO & SSO and disable Single Sign On.
When you disable SAML in Fill, your team members will be notified that SAML has been disabled and they should sign in using custom credentials.
Your Team members will receive a system generated email during the following events:.