Skip to content
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

Closed
5 tasks
julialawrence opened this issue Feb 15, 2024 · 9 comments
Closed
5 tasks

Integration of EntraID Identity into AWS SSO #6227

julialawrence opened this issue Feb 15, 2024 · 9 comments
Assignees
Labels
enhancement New feature or request member request Feature requested by a member to enhance the platform experience proof of concept single sign on

Comments

@julialawrence
Copy link
Contributor

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:

  1. Create an enterprise AAD connector in the Auth0 tenant that is supporting AWS SSO using these instructions
  2. As additional AAD permissions will be required to sync users from AAD to Identity Center, manually create between 4 and 6 users and a group within Identity Center to correspond to the users who are able to auth
  3. Potentially, prefix the created group with aad_ to avoid name clashes (this will require modifying the MP SSO code, and structure of environment json files)
  4. Experiment with customisation authentication experience options in Auth0 to minimise confusion
  5. Update one of AP environment files to assign a permission set to an AAD group
  6. Test authentication
  7. Stretch: Look at integrating one of our AP apps into SSO (not required, just nice to have)
  8. Capture findings
  9. Use findings to drive further identity converstions

Definition of Done

Example

  • Enterprise connection created
  • Users manually provisioned
  • AP environments file updated with new group
  • Authentication tested
  • Findings captured
@SimonPPledger
Copy link
Contributor

agreed to bring into this sprint after conversation with Julia

@markgov markgov self-assigned this Feb 27, 2024
@markgov
Copy link
Contributor

markgov commented Feb 27, 2024

Contacted john dryden and matthew white to dicuss the offical way fo getting an azures app setup for sso access to add to auth0

@markgov
Copy link
Contributor

markgov commented Feb 27, 2024

John Dryden
10:14
demand record which will then get passed to the EUCS IDAM team

@markgov
Copy link
Contributor

markgov commented Feb 27, 2024

spoken to Juila and she has already done the first part which is getting an app in azurse setup

@markgov
Copy link
Contributor

markgov commented Feb 29, 2024

PR created on sso repo for auth0
ministryofjustice/moj-terraform-aws-sso#51

@markgov markgov added enhancement New feature or request proof of concept single sign on member request Feature requested by a member to enhance the platform experience and removed needs refining labels Feb 29, 2024
@markgov
Copy link
Contributor

markgov commented Feb 29, 2024

  1. Julia to write temp Lambda SCIM for a few users
  2. Test temp Lambda SCIM works
  3. Import / provision Auth0 connection via code
  4. Merge and deploy 2 and 3 and test
  5. Request new Azure app with machine to machine permissions
  6. When received rewrite Lambda and switch secrets to new app

@markgov
Copy link
Contributor

markgov commented Mar 6, 2024

@markgov
Copy link
Contributor

markgov commented Mar 6, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request member request Feature requested by a member to enhance the platform experience proof of concept single sign on
Projects
Archived in project
Development

No branches or pull requests

3 participants