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

Update justice auth flow to use client_secret and prompt login #1282

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

michaeljcollinsuk
Copy link
Contributor

@michaeljcollinsuk michaeljcollinsuk commented Apr 5, 2024

Use the client_secret created in Azure app registration, for better security. This is set as an env var, and will be read from a Kubernetes secret, which will be added manually elsewhere. Also update azure client settings to always prompt the user to complete the login process with their justice identity. This will avoid confusion if a user is already logged in to their Justice identity.

In order to run locally, a new secret AZURE_CLIENT_SECRET needs to be added to your .env file. This is stored in the AP 1password vault, under the name "Control Panel Azure App Client Secrets"

Use the client_secret created in Azure app registration, for better
security. This is set as an env var, and will be read from a
Kubernetes secret, which will be added manually elsewhere.
Also update azure client settings to always prompt the user to
complete the login process with their justice identity. This will
avoid confusion if a user is already logged in to their Justice
identity.
Copy link
Contributor

@jamesstottmoj jamesstottmoj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally by adding new env var and running through login flow. Approved

@michaeljcollinsuk michaeljcollinsuk merged commit b45def2 into main Apr 5, 2024
5 checks passed
@michaeljcollinsuk michaeljcollinsuk deleted the feature/justice-identity-updates branch April 5, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants