Since Camel 3.1

The Elytron Security Provider provides Elytron security over the Camel Elytron component. It enables the Camel Elytron component to use Elytron security capabilities. To force Camel Elytron to use elytron security provider, add the elytron security provider library on classpath and provide instance of ElytronSecurityConfiguration as securityConfiguration parameter into the Camel Elytron component or provide both securityConfiguration and securityProvider into the Camel Elytron component.

Configuration has to provide all three security attributes:

Name Description Type


Builder for security domain.



MechanismName should be selected with regard to default securityRealm. For example, to use bearer_token security, mechanism name has to be BEARER_TOKEN and realm has to be TokenSecurityReal



Instance of WildFlyElytronBaseProvider with respect of mechanismName


Each exchange created by Undertow endpoint with Elytron security contains header securityIdentity with current Elytron’s security identity as value. (org.wildfly.security.auth.server.SecurityIdentity) or is FORBIDDEN (status code 403)

OSGi is not supported.

Maven users will need to add the following dependency to their pom.xml for this component:

    <!-- use the same version as your Camel core version -->

Other Elytron capabilities

This security provider contains only basic Elytron dependencies (without any transitive dependency from org.wildfly.security:wildfly-elytron). Ignored libraries should be added among application’s dependencies for their usage.