OpenID Connect (OIDC) Setup

1. In Security, select Authentication.

2. Under New single sign-on (SSO) on the Authentication settings page, select Manage SSO settings.

   If you are migrating an existing SSO connection, this option appears on the New single sign-on tab. Before you migrate, you can mange your existing connection on the Active single sign-on tab. After you migrate, the tabs no longer appear and you can no longer manage the old connection.

3. On the Single sign-on page, select OIDC.

4. Under Claim your email domains, select Claim domains or Edit claimed domains and specify the email domains that your organization uses. This allows you to recognize and redirect members to your IdP when they sign in. For instructions, see Claimed Email Domains.

1. Under Configure your connection on the Authentication settings page, select Get started or Edit connection.

2. On the Configure OIDC connection screen, enter a name to identify your organization's OIDC connection in the Connection name field.

3. To copy the redirect URL (https://id.blackbaud.com/bbid.onmicrosoft.com/oauth2/authresp), select Copy.

4. In a different browser tab, go to your IdP portal to register a new application or select an existing one on your OIDC domain. If your application requires a redirect URL, use the one you just copied.

   Warning: For an existing application, don't overwrite existing redirect URLs. If you remove the redirect URLs when you add the provided redirect URL, it can disrupt your existing SSO connection.

5. Return to Blackbaud's Configure OIDC connection screen, and in the Metadata URL field, enter the URL for the OIDC metadata document that contains information that is required during sign-in, such as the URLs to use and the location of the service's public signing keys. The metadata document is always located at an endpoint that ends in ".well-known/openid-configuration."

6. In the Response type field, select a response type. This determines the type of information that is sent back in the initial call to the authorization endpoint of your IdP.

   • To pass a token directly, select "ID Token." The ID token handles the generation of the client secret for SSO.

   • To pass a code that can then be exchanged for a token, select "Code." This does not handle the client secret generation, so you'll need to provide the client secret during configuration and then remember to update it before it expires.

7. In the Client ID field, enter the client ID for your OIDC project.

8. If you set the response type to "Code," enter the client secret for your OIDC project in the Client secret field.

9. In the fields under Confirm how your IdP identifies the following, specify where you store the data that your IdP uses to identify your organization's users. Enter field names or unique identifiers.

   Warning: You can only pass mapping fields if they are included under "claims_supported" in the OIDC metadata document that you provided in the Metadata URL field. That document, which ends in ".well-known/openid-configuration," contains information that is required during sign-in, such as the fields where you store data that identifies your users.

   1. In the NameID field, specify where you store the unique IDs that your IdP uses to identify your users. The field for this data varies depending on your IdP, but the values are typically not email addresses or employee IDs. Instead, the values should be unique IDs that your IdP creates to distinguish users across all accounts.

      We recommend against using email addresses to identify users. If you identify users by email address and need to change a user's email address, then you must re-invite the user at the new email address, which means you lose all history associated with the original one.

   2. In the Email address field, specify where you store user email addresses.

      For successful connections, email addresses must be unique.

   3. In the First name field, specify where you store first names.

   4. In the Last name field, specify where you store last names.

10. Select I acknowledge these changes can take up to 30 minutes to take effect. We recommend waiting 30 minutes before you test your SSO connection.

11. Select Save.

When you save your configuration settings, test mode is turned on automatically. At least one user must successfully sign in using test mode before you can enable your SSO connection.

To verify that your organization can use your identity provider (IdP) to sign in to Blackbaud solutions, select Learn about testing SSO under Test connection. Copy the URL under Blackbaud ID redirect and then test your connection in a in a private or incognito browser. For more information, see Test Mode.

Note: If a consent screen appears in test mode, then that means your IdP is configured to require admin approval before users authenticate. This consent screen is for the Blackbaud SSO application and is not requesting new permissions or access. It is seeking read-access to the user information that you already configured as part of your SSO setup. To proceed, follow the instructions on your IdP's consent screen.

To complete the connection to your IdP, select Turn on SSO under Turn on. Then on the Connect your OIDC SSO screen, select Connect with OIDC.

After you turn on SSO, users are redirected to your IdP when they sign in to their Blackbaud IDs with one of your claimed domains. After they authenticate through your IdP, their Blackbaud IDs:

• Automatically redirect them to your organization's login for future sign-ins.

  After users sign in through your organization's login, they are redirected to their Blackbaud ID profiles unless you edit the redirect to specify a Blackbaud solution. For more information, see Redirect Settings.

• Use your IdP for password updates, lockouts, and other authentication management.

Note: After you enable SSO, resend any pending invitations.