-
Notifications
You must be signed in to change notification settings - Fork 0
Analyst logs in using their dot.ca.gov account #43
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
Conversation
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Doc Ritezel <[email protected]>
Signed-off-by: Rae Bonfanti <[email protected]>
Signed-off-by: Rae Bonfanti <[email protected]>
3ff2a8c
to
ef7fc4a
Compare
f6a28e5
to
ae886ed
Compare
The changes look good to me but I do not know much about Django. Since the demo looked good, I think we can move forward. |
src/cal_bc/settings.py
Outdated
# See https://docs.djangoproject.com/en/5.2/howto/deployment/checklist/ | ||
|
||
# SECURITY WARNING: keep the secret key used in production secret! | ||
SECRET_KEY = "django-insecure-ehx7$j12*11z320lod=w9*kzgq*16)8s9+q_6)x%05#j#29uqa" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this dev key is okay to be pushed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely not once we deploy the app (we aren't yet). In any case, I'm going to go ahead and migrate this key to .env
. Good catch.
@shweta487 ok sounds good. I addressed and corrected for the issue you pointed out. Would you be willing to approve this PR? Thanks! |
Thank you for making the change. We can merge this. |
Summary
This PR adds OIDC-based authentication via Caltrans' Microsoft Azure Entra ID.
Resolves [#36] and [#42]
Type of change
Acceptance notes
To accept this PR, you will need to start the application locally by following the setup instructions in
README.md
. You will also need a set of credentials for the.env
file, as noted in those instructions, which @raebot or @ohrite can provide.Post-merge actions
No further action is required.