Bugfender can establish a trust relationship with your Identity Provider for a given domain, so that users can use your company's Single Sign-On system and seamlessly work with Bugfender without the need of a password.

For example, if your domain is yourcompany.com, Bugfender can trust your SSO system to authenticate all emails in the @yourcompany.com domain.

Automatic provisioning and de-provisioning

User accounts are automatically populated from your Identity Provider information when someone uses Bugfender for the first time. De-provisioned users can not log in to Bugfender anymore.

Supported software

Bugfender works with all SAML-enabled Identity Providers, including:

  • Okta

  • Ping Identity

  • Shibboleth

  • Active Directory

SAML Setup

If you would like to authenticate your domain with SAML, please get in touch with us. You will need to provide the following information:

  • The name of the domain(s) you want to authenticate with SAML, for example, yourcompany.com.

  • The SAML metadata URL of your Identity Provider.

During the setup of your Identity Provider you will need the metadata URL of Bugfender: https://dashboard.bugfender.com/saml

Once you provide this information, we'll follow together the following steps:

  • Verify the ownership of the domain

  • Set up the SAML connection between your Identity Provider and Bugfender

  • Test the login using the Identity Provider

  • (Optionally) Make your Identity Provider the authoritative source for logins on your domain, removing the possibility of logging in in other ways

Attribute mappings

Bugfender requires SAML responses to assert:

  • The user's email address: Email or urn:oid:0.9.2342.19200300.100.1.3 or urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

  • The user's name: urn:oid:2.16.840.1.113730.3.1.241 or FirstName and LastName

Attribute mappings for Ping Identity

Please set up the mappings like this:

Did this answer your question?