-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration of EntraID Identity into AWS SSO #6227
Comments
agreed to bring into this sprint after conversation with Julia |
Contacted john dryden and matthew white to dicuss the offical way fo getting an azures app setup for sso access to add to auth0 |
John Dryden |
spoken to Juila and she has already done the first part which is getting an app in azurse setup |
PR created on sso repo for auth0 |
|
User Story
As a modernisation platform customer, I would like to be able to use my justice identity to authenticate with AWS. This would allow users who aren't on Github to get access as well as align us with the general movement towards a single unified identity across MOJ.
Value / Purpose
Each additional source of identity introduces both an operational and security overhead and additionally, having a single source of identity simplifies user onboarding, and the JML process as a whole.
Useful Contacts
@julialawrence
Additional Information
This is likely to be as POC in advance of requesting additional AAD permissions from Tech Services to support full deployment.
Initially, an AzureAD app with delegated User.Read permissions will suffice but a fully solution will need more permissions.
Proposal / Unknowns
Hypothesis
If we... start by integrating AAD as a identity provider for Auth0
Then...when we switch over, we will be able to reuse these identities in AWS Identity Center
Proposal
The following POC:
aad_
to avoid name clashes (this will require modifying the MP SSO code, and structure of environment json files)Definition of Done
Example
The text was updated successfully, but these errors were encountered: