Jetty component is unable to be configured for security
-------------------------------------------------------

                 Key: CAMEL-1570
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1570
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-jetty
    Affects Versions: 2.0-M1, 1.6.0
         Environment: NA
            Reporter: Christopher Hunt


The Jetty component is presently unable to be configured for security. A 
general purpose mechanism so that the Jetty component can be configured would 
be useful. The following URI based option is proposed:

||Name||Default Value||Description||
|handlers|null| Specifies a comma delimited set of instances in your Registry 
(such as your Spring ApplicationContext). This instances are added to the Jetty 
servlet context|

Here is an example URI:

{code}
jetty:http://0.0.0.0:9080/MyService?handlers=securityHandler
{code}

This could refer to something like the following Spring configuration:

{code}
        <!-- Jetty Security handling -->
        <bean id="userRealm" class="org.mortbay.jetty.plus.jaas.JAASUserRealm">
                <property name="name" value="tracker-users" />
                <property name="loginModuleName" value="ldaploginmodule" />
        </bean>
        <bean id="constraint" class="org.mortbay.jetty.security.Constraint">
                <property name="name" value="BASIC" />
                <property name="roles" value="tracker-users" />
                <property name="authenticate" value="true" />
        </bean>
        <bean id="constraintMapping" 
class="org.mortbay.jetty.security.ConstraintMapping">
                <property name="constraint" ref="constraint" />
                <property name="pathSpec" value="/*" />
        </bean>
        <bean id="securityHandler" 
class="org.mortbay.jetty.security.SecurityHandler">
                <property name="userRealm" ref="userRealm" />
                <property name="constraintMappings" ref="constraintMapping" />
        </bean>
{code}

I have attached proposed changes to the 1.6 branch. I imagine that 2.0 should 
be quite similar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to