[
https://issues.apache.org/jira/browse/CAMEL-18806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18806.
---------------------------------
Resolution: Won't Fix
> camel-core - Allow to restrict Camel routes from using specific components,
> properties function etc
> ---------------------------------------------------------------------------------------------------
>
> Key: CAMEL-18806
> URL: https://issues.apache.org/jira/browse/CAMEL-18806
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: Future
>
>
> With Camel being able to run routes in an easier way from scripts and other
> DSLs in a low-code / camel-k fashion, then there is also a demand for being
> able to restrict what these routes can do with Camel itself.
> Camel is very powerful and tradtionally in the hands of Java developers they
> are able to control these powers.
> What we need to find out is some kind of "light RBAC" for Camel routes that
> these kind of users are running. And also at the same time we should allow
> pre-build kamelets / routes that have been "pre-approved" to not be
> restricted. For example some shared/common JAR with routes that may do more
> advanced stuff or handling errors etc.
> There are many places in CamelContext that are in use while loading a route.
> So we need to find out a good way for this.
> - components
> - data formats
> - languages
> - invoking bean
> - DSLs that can be used
> - property placeholder / functions (eg ENV function)
> - simple language (may restrict advanced features ala OGNL and whatnot)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
