Hi,

Yes, pax-web can provide this flexibility IMO.

You can configure pax-web to support SSL, even in another port.[1]

And the http basic auth configuration actually is endpoint|bundle specific, not 
much about the transport level. For example, for cxf endpoint you can configure 
a authenticationInterceptor(it could be 
org.apache.cxf.interceptor.security.JAASLoginInterceptor) which can delegate 
the authentication to Karaf JAAS if this cxf endpoint need http basic auth, we 
have an example in SMX code base, you may wanna take a look.[2]

[1]https://ops4j1.jira.com/wiki/display/paxweb/SSL+Configuration
[2]https://svn.apache.org/repos/asf/servicemix/smx4/features/trunk/examples/cxf/cxf-ws-security-osgi/
-------------
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋

www.camelone.org : The open source integration conference: 

On 2013-6-5, at 上午11:49, m.mcinness1 wrote:

> Thanks for the replies.
> 
> Freeman, my use case is to interface with a number of third-party vendors,
> each having unique requirements and accessing very different applications.
> For example, one may require that the endpoint be restricted to ssl, another
> may require basic auth, and third might support neither. The services have
> no relationship to each other. In essence they are all private and custom to
> the third parties.
> 
> I've read a couple posts regarding proxying via camel and modifying
> jetty.xml with pax web, but it's not clear whether either of these would be
> a better choice for my situation than stand alone jetty and multiple ports.
> We'll end up running 20 or so application bundles on one karaf instance.
> Does pax web offer the flexibility we need?
> 
> Thanks again!
> 
> 
> 
> 
> --
> View this message in context: 
> http://karaf.922171.n3.nabble.com/Jetty-and-multiple-jaxrs-servers-tp4028957p4028962.html
> Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to