nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changes to the OAuth Token Responses

Lindsey Rix

A new shared changelog was posted on 4/17/2020. See the changelog for more information.

OAuth token responses have been updated to include additional information about the consenting user. After login, the user will now be asked to provide consent for your application to access their Blackbaud data and user information.

If the user grants access and the access token request is successful, you will now see the following additional fields in the token response body:

email – The email address of the authenticated Blackbaud user.
family_name – The last name of the authenticated Blackbaud user.
given_name – The first name of the authenticated Blackbaud user.

Find more posts tagged with

Comments

Himal Patel

That's a great news. For whatever reason, we are still not receiving this fields in the token. Is there anything we are missing/change on our side ?

Lindsey Rix

Hi Himal,

Are you looking for the new fields in the authorization code flow or implicit flow? This doesn't yet apply for the user identity token for add-ins because we don't have a workflow that allows user consent.