Migration From OpenESb V2.2 to standalone 3.0.5 SecurityRealm Configuration

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Migration From OpenESb V2.2 to standalone 3.0.5 SecurityRealm Configuration

OpenESB Community Forum mailing list
Hi All,

I had added ws-security in my openESB v2.2 project and it was working fine,
but when I deployed the same project on openESB standalone v3.0.5 and tested
it faced below exception. I don't know how to define security realm
configuration in openesb.yaml file. Below is my current configuration for
realm. Is there anyone who can tell me that whats the issue with my given
configuration?

*openesb.yaml*
realm:
   # The realm "management" is the realm used for management (JMX / Rest API
/ oeadmin)
   management:
      type: properties
      file: ${openesb.home}/config/mgmt-users.properties
   file:
      type: properties
      file: ${openesb.home}/config/keyfile


*EXCEPTION*
2018-01-29T21:10:53.033+0500 SEVERE
[javax.enterprise.resource.xml.webservices.security]
(httpWorkerThread-9080-0) WSS0225: Exception occured in Password Validation
Callback
com.sun.xml.wss.XWSSecurityException: Error: Could not locate default
username validator for the container
        at
com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.authenticate(DefaultRealmAuthenticationAdapter.java:197)
        at
com.sun.xml.wss.RealmAuthenticationAdapter.authenticate(RealmAuthenticationAdapter.java:93)
        at
com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.authenticateUser(DefaultSecurityEnvironmentImpl.java:1172)
        at
com.sun.xml.ws.security.opt.impl.incoming.UsernameTokenHeader.validate(UsernameTokenHeader.java:160)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.handleSecurityHeader(SecurityRecipient.java:357)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.cacheHeaders(SecurityRecipient.java:291)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:241)
        at
com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:450)
        at
com.sun.xml.wss.jaxws.impl.SecurityServerTube.processRequest(SecurityServerTube.java:295)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:961)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873)
        at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:717)
        at com.sun.xml.ws.api.pipe.Fiber.start(Fiber.java:418)
        at
com.sun.xml.ws.server.WSEndpointImpl.processAsync(WSEndpointImpl.java:364)
        at com.sun.xml.ws.server.WSEndpointImpl.process(WSEndpointImpl.java:370)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:519)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:483)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:411)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:226)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at
com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
        at
com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

2018-01-29T21:10:53.033+0500 SEVERE
[javax.enterprise.resource.xml.webservices.security]
(httpWorkerThread-9080-2) WSS0225: Exception occured in Password Validation
Callback
com.sun.xml.wss.XWSSecurityException: Error: Could not locate default
username validator for the container
        at
com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.authenticate(DefaultRealmAuthenticationAdapter.java:197)
        at
com.sun.xml.wss.RealmAuthenticationAdapter.authenticate(RealmAuthenticationAdapter.java:93)
        at
com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.authenticateUser(DefaultSecurityEnvironmentImpl.java:1172)
        at
com.sun.xml.ws.security.opt.impl.incoming.UsernameTokenHeader.validate(UsernameTokenHeader.java:160)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.handleSecurityHeader(SecurityRecipient.java:357)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.cacheHeaders(SecurityRecipient.java:291)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:241)
        at
com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:450)
        at
com.sun.xml.wss.jaxws.impl.SecurityServerTube.processRequest(SecurityServerTube.java:295)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:961)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873)
        at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:717)
        at com.sun.xml.ws.api.pipe.Fiber.start(Fiber.java:418)
        at
com.sun.xml.ws.server.WSEndpointImpl.processAsync(WSEndpointImpl.java:364)
        at com.sun.xml.ws.server.WSEndpointImpl.process(WSEndpointImpl.java:370)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:519)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:483)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:411)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:226)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at
com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
        at
com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

2018-01-29T21:10:53.047+0500 SEVERE [com.sun.xml.wss.jaxws.impl]
(httpWorkerThread-9080-0) WSSTUBE0025: Error in Verifying Security in the
Inbound Message.
com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException:
Error: Could not locate default username validator for the container
        at
com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.authenticateUser(DefaultSecurityEnvironmentImpl.java:1179)
        at
com.sun.xml.ws.security.opt.impl.incoming.UsernameTokenHeader.validate(UsernameTokenHeader.java:160)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.handleSecurityHeader(SecurityRecipient.java:357)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.cacheHeaders(SecurityRecipient.java:291)
        at
com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:241)
        at
com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:450)
        at
com.sun.xml.wss.jaxws.impl.SecurityServerTube.processRequest(SecurityServerTube.java:295)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:961)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873)
        at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:717)
        at com.sun.xml.ws.api.pipe.Fiber.start(Fiber.java:418)
        at
com.sun.xml.ws.server.WSEndpointImpl.processAsync(WSEndpointImpl.java:364)
        at com.sun.xml.ws.server.WSEndpointImpl.process(WSEndpointImpl.java:370)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:519)
        at
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:483)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:411)
        at
com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:226)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at
com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
        at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
        at
com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
Caused by: com.sun.xml.wss.XWSSecurityException: Error: Could not locate
default username validator for the container
        at
com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.authenticate(DefaultRealmAuthenticationAdapter.java:197)
        at
com.sun.xml.wss.RealmAuthenticationAdapter.authenticate(RealmAuthenticationAdapter.java:93)
        at
com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.authenticateUser(DefaultSecurityEnvironmentImpl.java:1172)
        ... 24 more



--
Sent from: http://openesb-community-forum.794670.n2.nabble.com/