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

🔱 Investigate enabling EntraID auth to Control Panel #6518

Open
5 tasks
tom-webber opened this issue Jan 7, 2025 · 0 comments
Open
5 tasks

🔱 Investigate enabling EntraID auth to Control Panel #6518

tom-webber opened this issue Jan 7, 2025 · 0 comments
Labels
spike investigation, discovery into a thing

Comments

@tom-webber
Copy link
Contributor

Context

We currently have a requirement for Analytical Platform Control Panel users to have a GitHub user that is associated with the moj-analytical-services organisation. We also subsequently link their Control Panel user to their EntraID login.

Relaxing the requirement for a GitHub login will lower the barrier to entry for the platform, but could potentially lose us untracked benefits associated with this integration.

Proposal

Investigate the requirements and consequences of moving to EntraID authentication, with or without the existing GitHub and Auth0 logins.

Spike requirements

Any, 3 days

Definition of Done

Example

  • Enumerate benefits of current auth mechanisms
    • GitHub integration
    • Auth0 integration
  • Work out what we would lose by eliminating either or both existing auth mechanisms
  • Determine requirements for enabling EntraID auth for Control Panel
@tom-webber tom-webber added the spike investigation, discovery into a thing label Jan 7, 2025
@tom-webber tom-webber moved this to 👀 TODO in Analytical Platform Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike investigation, discovery into a thing
Projects
Status: 👀 TODO
Development

No branches or pull requests

1 participant