Docs
Other SAML 2.0 identity provider
Any identity provider that speaks SAML 2.0 works if it can sign assertions with RSA-SHA256 and post them to this workspace. Set it up with the values below and give Flipbird its metadata.
-
Create a SAML 2.0 application
In your identity provider, create a SAML 2.0 service provider (sometimes called a relying party or an app).
If it can read service provider metadata, give it the metadata URL below and skip to the attributes.
Service provider metadata URL
https://your-workspace.flipbird.io/api/sso/metadata -
Service provider settings
Set the entity ID (also called audience or identifier) and the Assertion Consumer Service URL, with the HTTP-POST binding.
Sign the assertion (the response may be signed too) with RSA-SHA256 or stronger. Do not encrypt assertions.
Entity ID / Audience
https://your-workspace.flipbird.io/api/sso/metadataAssertion Consumer Service URL
https://your-workspace.flipbird.io/api/sso/acsSign-in URL (for SP-initiated sign-in)
https://your-workspace.flipbird.io/api/sso/login -
Name ID and attributes
Send the person's email address as the NameID, in the emailAddress format.
Send attributes named email, firstName and lastName. Optionally send groups, to map groups to Flipbird roles.
NameID format
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress -
Give Flipbird the IdP's details
Paste the identity provider's metadata URL or upload its metadata file. Without metadata, enter its entity ID, its HTTP-Redirect sign-on URL and its signing certificate.
-
Test in Flipbird
Run Test sign-in. Require SAML only after the test succeeds.
What Flipbird reads
Name ID: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress, from The person's email address.
| Attribute | From | Used for |
|---|---|---|
email | Email address | Email address (required) |
firstName | Given name | First name |
lastName | Family name | Last name |
groups | Group names | Groups, for role mapping |