You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/05/14 04:12:00 UTC
[jira] [Resolved] (CAMEL-16606) Allow specifying security
requirement(s) applicable to entire API
[ https://issues.apache.org/jira/browse/CAMEL-16606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-16606.
---------------------------------
Fix Version/s: (was: 3.11.0)
3.10.0
Resolution: Fixed
> Allow specifying security requirement(s) applicable to entire API
> -----------------------------------------------------------------
>
> Key: CAMEL-16606
> URL: https://issues.apache.org/jira/browse/CAMEL-16606
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, rest
> Affects Versions: 3.9.0
> Reporter: Shankar Ramamoorthy
> Priority: Major
> Fix For: 3.10.0
>
>
> In the Camel REST DSL one can specify security requirements per endpoint. But there isn't a way to specify security requirement(s) applicable to all endpoints. In the OpenAPI 3 schema this corresponds to a security section at the root level.
> Perhaps this can be done by just using the existing
> {{RestDefinition.security(String name [, String scopes])}}
> but allow it to be called without a verb, in which case it would apply to the entire API.
> {{In generated OpenAPI 3 JSON schema this would produce a root level node such as: "security": [ \{"api_key": []}] or "security": [\{"oauth2_auth": [ "read", "write" ]}]}}
> Currently if you do, for example, rest().security(scheme), you get an IllegalArgumentException that one "Must add verb first, ..."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)