-
Notifications
You must be signed in to change notification settings - Fork 10
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
EREGCSC-2041 -- Set up url and configs for OIDC #914
Conversation
@@ -4,7 +4,7 @@ jobs: | |||
gitleaks-scan: | |||
runs-on: ubuntu-latest | |||
steps: | |||
- uses: actions/checkout@v2 | |||
- uses: actions/checkout@v3 |
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.
Gitleaks had a warning for using v2 being old so I just changed it to v3. Documentation for gitleaks github action also has it using v3 currently.
OIDC_RP_CLIENT_SECRET = os.environ.get("OIDC_RP_CLIENT_SECRET", None) | ||
OIDC_OP_AUTHORIZATION_ENDPOINT = os.environ.get("OIDC_OP_AUTHORIZATION_ENDPOINT", None) | ||
OIDC_OP_TOKEN_ENDPOINT = os.environ.get("OIDC_OP_TOKEN_ENDPOINT", None) | ||
OIDC_OP_USER_ENDPOINT = os.environ.get("OIDC_OP_USER_ENDPOINT", None) |
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.
putting all of these values into environment variables until we figure out what is a secret and what isnt. Since we dont actually have the token stuff yet we have to set them to none. no impact on the application
✨ See the Django Site in action ✨ |
✨ See the Django Site in action ✨ |
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.
LGTM
Resolves # EREGCSC-2041
Description-
In order for us to set up oAuth we need a call back url. This is getting us set up.
This pull request changes...
Steps to manually verify this change...