Hello Jean-Baptiste, Thanks for your answer and you help. I did already your suggested 2nd approach as you can read here:
http://camel.465427.n5.nabble.com/Adding-jaas-authentication-to-a-cxf-endpoint-in-karaf-td5758340.html However it is not that easy. I think it has something to do how the camel cxf consumer route is connected to the jetty settings in blueprint.xml: <camelcxf:cxfEndpoint id="warehouseService" wsdlURL="wsdl/externalWarehouseService.wsdl" serviceClass="de.company.production.externalwarehouse.ws.ExternalWarehousePortTypeImpl" address="http://localhost:9000/externalWarehouse"; loggingFeatureEnabled="true"> <bean id="loginService" class="org.eclipse.jetty.plus.jaas.JAASLoginService"> <property name="name" value="karaf" /> <property name="loginModuleName" value="karaf" /> <property name="roleClassNames"> <list> <value>org.apache.karaf.jaas.modules.RolePrincipal</value> </list> </property> </bean> <bean id="identityService" class="org.eclipse.jetty.security.DefaultIdentityService" /> ... <httpj:engine-factory bus="cxf"> <httpj:engine port="9000"> <httpj:threadingParameters minThreads="5" maxThreads="20" /> <httpj:handlers> <ref component-id="securityHandler" /> </httpj:handlers> </httpj:engine> </httpj:engine-factory> It seems here is something missing or wrong or totally misunderstood. The web service should run under conventional http and not via https/SSL. Kind regards, Hilderich -- View this message in context: http://karaf.922171.n3.nabble.com/camel-cxf-endpoint-with-Basic-Auth-via-jaas-in-Karaf-tp4036163p4036174.html Sent from the Karaf - User mailing list archive at Nabble.com.
