Docs

Microsoft Entra ID

Create a non-gallery enterprise application in your Microsoft Entra tenant, point its SAML settings at this workspace, and give Flipbird the application's federation metadata URL.

Version 1 · checked on

  1. Create the application

    Where: Entra ID › Enterprise apps › All applications › New application › Create your own application

    Sign in to the Microsoft Entra admin center (entra.microsoft.com) as at least a Cloud Application Administrator.

    Name the application Flipbird, choose "Integrate any other application you don't find in the gallery (Non-gallery)", and select Create.

  2. Choose SAML

    Where: Manage › Single sign-on › SAML

    In the new application, open Single sign-on from the Manage section and select SAML.

  3. Basic SAML Configuration

    Where: Basic SAML Configuration › Edit

    Replace any sample values with the ones below, then select Save.

    Leave Relay State and Logout Url empty.

    Identifier (Entity ID)

    https://your-workspace.flipbird.io/api/sso/metadata

    Reply URL (Assertion Consumer Service URL)

    https://your-workspace.flipbird.io/api/sso/acs

    Sign on URL (Optional)

    https://your-workspace.flipbird.io/api/sso/login
  4. Attributes & Claims

    Where: Attributes & Claims › Edit

    Open Unique User Identifier (Name ID). Set Name identifier format to Email address and Source attribute to user.mail, then Save.

    Keep the default emailaddress, givenname and surname claims.

    Optional, to map groups to Flipbird roles: select Add a group claim, choose Groups assigned to the application (or Security groups), and Save. Entra sends each group's object ID, and sends no groups at all for someone in more than 150, so prefer groups assigned to the application.

    Name identifier format

    urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
  5. Copy the metadata URL

    Where: SAML Certificates

    Copy App Federation Metadata Url and paste it into Flipbird. If you prefer a file, download Federation Metadata XML instead.

    Leave token encryption off: Flipbird refuses encrypted assertions.

  6. Choose who can sign in

    Where: Manage › Users and groups › Add user/group

    Assign the people or groups who should use Flipbird. People you do not assign cannot sign in through this application.

  7. Test in Flipbird

    Back in Flipbird, import the metadata URL and 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 user.mail.

AttributeFromUsed for
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddressuser.mailEmail address (required)
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givennameuser.givennameFirst name
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surnameuser.surnameLast name
http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsGroup claim (group object IDs)Groups, for role mapping

The provider's own documentation