Set up SSO

Single sign-on (SSO) is a way for lenders to handle access control for their employees who need to access multiple services using one service. There are several platforms that can help you accomplish this task such as Okta, AzureAD, Pind Fedra, and ADFS. Built can help you set up and enable SSO for your employees so you can add it to your SSO platform, mitigating internal risks and making access more efficient for your employees.

Set up SSO with Built

Setting up SSO with Built is a coordinated process between you and your Implementation Manager or Client Success Manager. We’ve outlined the process below for your reference:  

  1. Reach out to your Implementation Manager or Client Success Manager to let them know you are interested in setting up SSO for your institution. 

  2. After confirming that SSO is part of your statement of work, configure a test application within your Identity Provider (IdP) to support SSO with SAML 2.0 (Security Assertion Markup Language). A member of your IT team can complete this process for your institution. The email attribute is the only SAML attribute we need from your configuration.

  3. Email your Implementation Manager or Client Success Manager the SAML 2.0 metadata URL for the test application. If you don’t have the metadata URL available, you can export and email the SAML metadata XML with the application client id. We will return the following information for you to complete the setup.

    • Login URLs

    • Users created within the Built test instance

    • Audience URI (uniform resource identifier)

    • SSO response URL

    • SSO initiate URL

  4. Using the Audience URI, SSO response URL, and SSO initiate URL, finish configuring the application in your IdP.

  5. Associate the application with the appropriate users in your IdP using the list of users created in the test instance.

  6. Have the associated users log in with SSO. If they have any issues, have them take screenshots and email them to your Implementation Manager or Client Success Manager so we can help troubleshoot.

After completing these steps, we’ll repeat the process for enabling SSO in your production environment. Reach out via email to your Implementation Manager or Client Success Manager if you have any questions.  

Logging in after SSO set up

After setting up SSO for your organization, you can log in through your SSO platform to access Built. Some platforms enable you to create bookmarks for your Built login URL like Okta.


FAQ

What is Single Sign-On (SSO)?

Single Sign-On (SSO) is a method that allows employees to access multiple services using one set of login credentials.

Which platforms can help set up SSO?

Platforms such as Okta, AzureAD, Pind Fedra, and ADFS can assist in setting up SSO.

How can Built assist with SSO setup?

Built can help you set up and enable SSO for your employees, making access more efficient and mitigating internal risks.

What is the first step to set up SSO with Built?

The first step is to reach out to your Implementation Manager or Client Success Manager to express your interest in setting up SSO.

What is required from the Identity Provider (IdP) for SSO configuration?

You need to configure a test application within your IdP to support SSO with SAML 2.0, providing the email attribute as the only SAML attribute needed.

What should I do if users encounter issues logging in after SSO setup?

If users have issues, they should take screenshots of the problems and email them to your Implementation Manager or Client Success Manager for troubleshooting.

Can I log in to Built after SSO setup?

Yes, after setting up SSO, you can log in through your SSO platform to access Built.

Is it possible to create bookmarks for the Built login URL?

Yes, some platforms like Okta allow you to create bookmarks for your Built login URL.