[
https://issues.apache.org/jira/browse/CAMEL-16609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344613#comment-17344613
]
Shankar Ramamoorthy edited comment on CAMEL-16609 at 5/14/21, 2:02 PM:
-----------------------------------------------------------------------
Differences between OpenAPI 3.1 spec and current Camel code:
* Security scheme "type" is missing "mutualTLS" and "openIdConnect"
* OAuth2:
** "application" flow is now called "clientCredentials"
** "refreshUrl" field is missing; from spec I think this is applicable to all
flows
* API Key: is missing "in" option "cookie"
* For "type" = "http" is missing scheme "bearer" which has field "bearerFormat"
was (Author: maqroll):
Differences between OpenAPI 3.1 spec and current Camel code:
* Security scheme "type" is missing "mutualTLS" and "openIdConnect"
* OAuth2:
** "application" flow is now called "clientCredentials"
** "refreshUrl" field is missing; from spec I think this is applicable to all
flows
* For "type" = "http" is missing scheme "bearer" which has field "bearerFormat"
> rest dsl - Add more security models for JWT bearer tokens etc
> -------------------------------------------------------------
>
> Key: CAMEL-16609
> URL: https://issues.apache.org/jira/browse/CAMEL-16609
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, rest
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.11.0
>
>
> There are some newer security models in openapi spec v3 which we dont yet
> have in the rest-dsl model.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
