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
Disable authentication for DCR create via tenant-wise config #269
Disable authentication for DCR create via tenant-wise config #269
Changes from 12 commits
86b116c
c5cdcd4
2cdf93d
bef486a
cf15335
ec72d06
be5add7
0670d29
90d18ba
0b159f1
1a9357b
93eeaf0
067e2a6
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.
can simplify the if , else
securedResource.setIsSecured(Boolean.TRUE.equals(isClientAuthenticationRequired));
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.
This was not done because then if
isClientAuthenticationRequired
isnull
(isClientAuthenticationRequired
is not set),Boolean.TRUE.equals(isClientAuthenticationRequired)
value will be False, which is incorrect.If
isClientAuthenticationRequired
is not set, it should be the current default behaviour, where securedResource.isSecured will be True.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.
In that case, we can specially handle using the clause if(isClientAuthenticationRequired ==null)
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 think we should not handle the scenario where
isClientAuthenticationRequired
is not set, because it can change the current flow.This is a tenant-level config and this overrides the server level configs. If tenant-level config is not set, the server level config should be there.
IS has a config in deployment.toml to configure api security for any endpoint using the endpoint url pattern. For DCR if
isClientAuthenticationRequired
is not set, that config value (if configured) will change thesecuredResource.isSecured
value.