[jira] Commented: (CAMEL-1570) Jetty component is unable to be configured for security

["Christopher Hunt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51553#action_51553 ] 

Christopher Hunt commented on CAMEL-1570:
-----------------------------------------

Hi Claus,

1.x patches attached. I have not addressed 2.0. With regards to:

_In Camel 2.0 however I was wondering if we should endorse the # notation lookup that is used in the URI to refer to a bean in the registry with this id._

I think so.

_And if we just added the type on the endpoint as: List<Handler> handlers with getter/setter then we can improve the DefaultComponent to support lists for its automatic # lookup._

Do you mean List<String> not List<Handler>? Or do you think that the DefaultComponent could resolve the type from the bean's name?

_Today it only supports a single # property. If so we get a general solution. So I would like that we took the time to look into this in Camel 2.0._

How would a list be expressed in the URI? The same way as for 1.x i.e. using a comma?

_See method setReferenceProperties in DefaultComponent in Camel 2.0._

I'm going to need your help on this one I think.

> 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: 1.6.0, 2.0-M1
>         Environment: NA
>            Reporter: Christopher Hunt
>         Attachments: jetty-handlers-test.txt, jetty-handlers.txt
>
>
> 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). These 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.