Skip to content

Conversation

@bennettn4
Copy link
Contributor

Ticket: (https://broadworkbench.atlassian.net/browse/TOAZ-363)

What:

UAMI accounts do not have OIDC_email field populated through accesstoken, need to be dynamically built from b2cid

Why:

Needed if Thurloe is running as a user assigned managed identity on azure and needs service account admin whitelist

How:

Additional check in service account admin whitelist based UAMI email


PR checklist

  • I've followed the instructions if I've made any changes to the API, especially if they're breaking changes
  • I've filled out the Security Risk Assessment (requires Broad Internal network access) and attached the result to the JIRA ticket

UAMI accounts will not have oidc email field populated through token, need to be dynamically built
Needed if Thurloe is running as an UAMI and needs service account admin whitelist
bennettn4 added 2 commits July 1, 2024 10:29
Swapped boolean logic to allow if either condition is true as opposed to reject if both conditions are false
Added helper function to verify email oidcHeader is empty to clean up logic in route slightly and remove edge case of [email protected] being a potentially valid value in serviceAccountAdmin configuration
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 1, 2024

@bennettn4 bennettn4 requested a review from dvoet July 2, 2024 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants