Devops/tweak openid for different access url #510
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Method to tweak base auth to allow usage of non-cac for service lookup and cac for user login through Swagger. - Implemented Functionality to process JWT and build appropriate DataApiPrincipal. Closes #392.
adamkorynta
reviewed
Jan 12, 2024
ktarbet
reviewed
Jan 12, 2024
compose_files/pki/certs/main.crt
Outdated
There was a problem hiding this comment.
I think several files in pki/certs/* area are re-generated and don't need to be included here?
cwms-data-api/src/main/java/cwms/cda/security/OpenIDConfig.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Karl Tarbet <ktarbet@users.noreply.github.com>
ktarbet
approved these changes
Jan 12, 2024
|
@MikeNeilson there is a way for users to update their profile, first name, last name and e-maiil anyway. we're working on getting that workflow documented. We don't have e-mail verification wired up so they all show not-verified even if there is an e-mail, probably something we need to get incorporated. |
adamkorynta
approved these changes
Jan 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was finally able to retrieve an active JWT and see how things worked. CDA can now use the EDIPI provided by the JWT to retrieve CWMS user credentials.
Possible future work involved database changes to allow use of the "sub" which would be appropriate to allow Keycloak Direct Grant OR Login.gov.
The majority the auth flows are not usable by our users, and some scopes don't work even through their presented. Removing the oauth flows is easy, I'll investigate later setting an appropriate default scope and client id.
Oh and for anyone that ever needs to try TLS/Mutual auth from a termina in windows:
Note with the above email did not show up within the JWT, @willbreitkreutz the JWT clearly said email not verified so seems reasonable to ; is there a process for a user to update their information on keycloak, couldn't quite figure out how to log in to my account correctly, assuming it's even configured to do so.