5:20 a.m.
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Marcus Moyses commented on JBWS-3255:
-------------------------------------
If it turns out you absolutely need to lookup the AuthenticationManager in JNDI (i.e. you
can't depend on AS7 services) use SecurityConstants.JAAS_CONTEXT_ROOT +
securityDomainName to lookup.
There is also a org.jboss.security.SecurityUtil.unprefixSecurityDomain method that might
come in handy to get the correct security domain name.
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 a.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3255:
----------------------------------
Fix Version/s: jbossws-native-4.0.0.Beta2
(was: jbossws-native-4.0)
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:19 p.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Steve Cohen commented on JBWS-3255:
-----------------------------------
I experience same using JBossAS-5.1.0,GA and JBossWS-native 3.4.0. I simply drop the
@EndpointConfig(configName = "Standard WSSecurity Endpoint")
annotation into my Port Impl class and I get the same errors.
If I understand Marcus Moyses's comment above correctly this means I need to create my
own version of org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer since the
one provided is tied to a JNDI name that is no longer valid as of 5.1.0 if not earlier.
Is that right? Or is another workaround available on 5.1.0?
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 p.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Steve Cohen commented on JBWS-3255:
-----------------------------------
Actually, it's not so easy as that the offending hardcoded JNDI name is in
AuthorizeOperation, not in WSSecurityHandler.
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3255:
---------------------------------------
Steve, disregard Marcus comment here, as that is valid on AS7 (this jira is child of
JBWS-3216, which was about failures against AS 7).
WS-Security should simple work with JBWS Native 3.4.0 on top of AS 5.1.0, just start from
one of the samples you can find in the jbossws-native testsuite.
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Steve Cohen commented on JBWS-3255:
-----------------------------------
Thanks Alessio, but my point is that it DOESN'T work with Native 3.4,0 on top of AS
5.1.0 in spite of your assertions that it SHOULD. Have you actually tried it?
For one thing, although the documentation included with the 3.4.0 Test Suite talks about a
JBossWS-Security And Attachments Sample supposedly located in the
org.jboss.test.ws.jaxws.samples.news package, this package does not in fact exist in the
3.4.0 Test Suite and there is no source code in the 3.4.0 Test Suite examples that
contains the @EndpointConfig annotation, although you can find it in the included
documentation, which, however, does not seem to pertain to 3.4.0. If 3.4.0 could do this,
there should be a sample illustrating how. Maybe there needs to be a 3.4.0a?
So I must ask: is it even possible to do WS Security with 3.4.0 over 5.1.0? And if so,
how? And, as we know from
http://community.jboss.org/wiki/JBossWS-SupportedTargetContainers, 3.4.1 is not compatible
with 5.1.0.
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:48 a.m.
New subject: [JBoss JIRA] (JBWS-3255) Unable to lookup AuthenticationManager
[
https://issues.jboss.org/browse/JBWS-3255?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3255:
---------------------------------------
Steve, you need to download the src distribution, the binary distribution only contains
stack-agnostic tests/samples. Within the src distro, you'll find for instance
jbossws-native-src-dist/modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wssecurity/UsernameBean.java
having such @EndpointConfig annotation.
Unless the test is not excluded through
jbossws-native-src-dist/modules/testsuite/test-excludes-jboss*.txt, the test has been
successfully run as part of the release process for the selected version. So yes, we
actually tried that, at the time of JBWS 3.4.0.GA release. Sure, it's possible to use
WS-Security from jbws-native on top of AS 5.1.0.
Please follow up on the forum if you need to, this jira issue is being derailed by this
discussion ;-)
Unable to lookup AuthenticationManager
--------------------------------------
Key: JBWS-3255
URL: https://issues.jboss.org/browse/JBWS-3255
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0.0.Beta2
12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
(http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable
to lookup AuthenticationManager
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
at
org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
[jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context
''
at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at
org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211)
[jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT]
at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20]
at
org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80)
[jbossws-native-core.jar:4.0.0-SNAPSHOT]
... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4785
days inactive
5031
days old
jbossws-issues@lists.jboss.org
7 comments
5 participants
participants (5)
-
Alessio Soldano (Commented) (JIRA) -
Alessio Soldano (Updated) (JIRA)
-
Marcus Moyses (JIRA)
-
Richard Opalka (JIRA)
-
Steve Cohen (Commented) (JIRA)