-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[JavaSpring] Enable scopes for all security scheme types #17083
[JavaSpring] Enable scopes for all security scheme types #17083
Conversation
a6c6665
to
1d134cd
Compare
1d134cd
to
79e02e6
Compare
cc |
Hi team, could you take a look? |
@@ -196,16 +196,16 @@ public interface {{classname}} { | |||
responseContainer = "{{{.}}}"{{/returnContainer}}{{#hasAuthMethods}}, | |||
authorizations = { | |||
{{#authMethods}} | |||
{{#isOAuth}} | |||
{{#scopes.0}} |
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.
Is this just using the first scope? Can/should this consider any additional scopes?
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.
Hi welshm, Thanks for your review.
This is idiom that checks if the array scopes
is not empty, which is already used in the many places of existing templates (ex: here, and here).
So when multiple scopes are specified...
security:
- bearer: [ foo, bar ]
It will be generated using all scopes as follows.
security = {
@SecurityRequirement(name = "bearer", scopes={ "foo", "bar" })
}
@@ -89,6 +90,16 @@ public CodegenSecurity (CodegenSecurity original) { | |||
public CodegenSecurity filterByScopeNames(List<String> filterScopes) { | |||
CodegenSecurity filteredSecurity = new CodegenSecurity(this); | |||
|
|||
// Since OAS 3.1.0, security scheme types other than "oauth2" and "openIdConnect" may have a list of role names |
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.
FYI @OpenAPITools/generator-core-team
fix: #17085
To Java technical committee: @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @martin-mfg (2023/08)
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming 7.1.0 minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)