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.
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
[AuthV2] Address Bug Bash feedback #3782
[AuthV2] Address Bug Bash feedback #3782
Changes from 5 commits
035dd97
43699e8
71c4a3c
833da57
8c934d2
bb74aca
c2c570c
e8c8e93
bae77a4
547de53
7a33e01
fd40d25
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Will this prevent customers from explicitly setting the
login.tokenStore.enabled
to False when enabling auth for the first time? If so, maybe we should default it to True only iflogin.tokenStore
isn't explicitly configured?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.
Do we need to worry about the case where
client_secret
is None? If I'm reading the code correctly (the indenting might be throwing me off), it seems like we'll try to set theclientSecretSettingName
regardless of whether a client secret was actually provided.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.
So per the code, if the client secret is not None, we set the app setting and set the clientSecretSettingName to whatever name we just gave that app setting we set. If client secret is none, we set clientSecretSettingName to the value of whatever is passed in to --client-secret-setting-name. If it's none, we leave it none, if it's not none, we set it to the specified value. Does that make sense, or do you recommend changing that?
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.
Makes sense. I forgot that when
client_secret
is none, it's likely becauseclient_secret_setting_name
was passed instead. Thanks!