3

我有一个SOAP webservice,在GlassFish 3.1.1运行的EAR的EJB子项目中使用绑定的Metro运行时使用@WebService声明。它已经在课堂上用通常的@DeclareRoles和@RolesAllowed进行了注释。对GlassFish领域的WS-Security UsernameToken进行身份验证会给出“身份验证被拒绝”

我有一个WSIT描述符用于使用简单的明文密码UsernameToken进行身份验证。

在EAR的glassfish-application.xml中,我将领域指定为GlassFish附带的标准文件领域。对于这个领域,我添加了一个用户进行测试,属于一个特定的组。该组映射到我在glassfish-ejb-jar.xml中指定的角色。

我还启用了GlassFish中的安全管理器以及审计。这样做后我重新启动了服务器。

我已经生成了一个客户端,并在回调处理程序中设置用户名和密码。我登录以确保证书确实设置。我也曾尝试设置这样的凭据:

Map<String, Object> requestContext = ((BindingProvider)port).getRequestContext(); 
requestContext.put(BindingProvider.USERNAME_PROPERTY, "myUsername"); 
requestContext.put(BindingProvider.PASSWORD_PROPERTY, "myPassword"); 

当我调用服务,我得到这个服务器上:

INFO: SEC5046: Audit: Authentication refused for [myUsername]. 
INFO: SEC1201: Login failed for user: myUsername 
SEVERE: WSS1408: UsernameToken Authentication Failed 
SEVERE: WSITPVD0035: Error in Verifying Security in Inbound Message. 
com.sun.xml.wss.impl.WssSoapFaultException: Authentication of Username Password Token Failed 
    at com.sun.xml.ws.security.opt.impl.util.SOAPUtil.newSOAPFaultException(SOAPUtil.java:158) 
    at com.sun.xml.ws.security.opt.impl.incoming.UsernameTokenHeader.validate(UsernameTokenHeader.java:164) 
    at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.handleSecurityHeader(SecurityRecipient.java:341) 
    at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.cacheHeaders(SecurityRecipient.java:275) 
    at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:225) 
    at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.verifyInboundMessage(WSITServerAuthContext.java:586) 
    at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:360) 
    at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:263) 
    at com.sun.enterprise.security.webservices.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:173) 
    at com.sun.enterprise.security.webservices.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:144) 
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:119) 
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641) 
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600) 
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585) 
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482) 
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:314) 
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:608) 
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:259) 
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:162) 
    at org.glassfish.webservices.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:120) 
    at org.glassfish.webservices.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:91) 
    at org.glassfish.webservices.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:200) 
    at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:131) 
    (Rest is snipped away) 

,我得到这个客户端上:

Authentication of Username Password Token Failed 
javax.xml.ws.soap.SOAPFaultException: Authentication of Username Password Token Failed 
    at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:189) 
    at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:189) 
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122) 
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119) 
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) 
    at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:140) 

然后我创建了一个简单的servlet/JSP项目,并在该领域添加了安全限制。在这种情况下使用相同用户的身份验证。

的WS-Security策略是这样的:

<ns1:Policy xmlns:ns1="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="MyServicePortBindingPolicy"> 
    <ns1:ExactlyOne> 
     <ns1:All> 
    <ns2:SupportingTokens xmlns:ns2="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"> 
     <ns1:Policy> 
     <ns1:ExactlyOne> 
      <ns1:All> 
     <ns2:UsernameToken ns2:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"> 
      <ns1:Policy> 
      <ns1:ExactlyOne> 
       <ns1:All> 
      <ns2:WssUsernameToken10 /> 
       </ns1:All> 
      </ns1:ExactlyOne> 
      </ns1:Policy> 
     </ns2:UsernameToken> 
      </ns1:All> 
     </ns1:ExactlyOne> 
     </ns1:Policy> 
    </ns2:SupportingTokens> 
    <ns3:UsingAddressing xmlns:ns3="http://www.w3.org/2006/05/addressing/wsdl" /> 
     </ns1:All> 
    </ns1:ExactlyOne> 
    </ns1:Policy> 

什么错吗?任何建议高度赞赏。

回答

1

当我禁用了我自己的homebaked程序认证机制时,它解决了这个问题,它引发了一个破坏性异常。不能相信,以前没有打我。