The route is secured with SSL and HTTP Basic Authentication using JAASLoginInterceptor and SimpleAuthorizingInterceptor interceptors. Now I want to secure WSDL on the camel-cxf consumer endpoint with HTTP Basic Authentication, similarly going through JAAS. Apache CXF, Services Framework - JAXRS OAuth2 Assertions Apache CXF: Index Note the clients can use assertions as grants but use for example Basic authentication mechanism, or use say an authorization code grant and the assertion to authenticate, and finally, they can use assertions as a JAX-WS Security Basic Authentication-1( WebService and Client) So CXF needs mechanisms for the user to set the config name and needs to provide CallBackHandlers to supply credentials. CallbackHandlers. CXF needs to supply different data to identify the users depending on the chosen authentication variant. Basic Auth: username and password from HTTP header Container or Spring Security managed authentication as well as the custom authentication are all the viable options used by CXF developers. Starting from CXF 2.3.2 and 2.4.0 it is possible to use an org.apache.cxf.interceptor.security.JAASLoginInterceptor in order to authenticate a current user and populate a CXF SecurityContext. Warning: count(): Parameter must be an array or an object that implements Countable in /homepages/23/d88768782/htdocs/main/wp-includes/class-wp-comment-query.php on Authentication and Authorization the CXF Way users dealing with WS-Security may not necessarily want to deal directly with the WSS4J library at the level of their CXF interceptors and AuthorizationPolicy capturing Basic or Digest authentication details. I created a new CXF Web Service with a Basic Authentication interceptor. I deploy it in WebLogic 10.3.6. When I invoke the web service the interceptor is not called. If I pass the weblogic user and password the interceptor is called. If I use an application user multiple times I get a message from WebLogic that the user is blo