An Internal Ws-security Error Occurred
not work correctly without it enabled. Please turn JavaScript back on and reload this page. All Places > JBoss Web Services > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 13 Replies Latest reply on Nov 21, 2012 2:07 PM by NOE GUTIERREZ Jboss ws-security, client configuration Tim de Jager May 17, 2010 4:31 AM Hello,I'm currently trying to secure a ws endpoint using the native jboss security stack. The server now sucessfully sign the message. I'm now trying to secure the client. It's a standalone java client using code generated by the jboss ws tool.I tried using the following code to enable ws-security from the client://port object obtained via SOAPService ((StubExt)port).setSecurityConfig(securityURL.toExternalForm()); ((StubExt)port).setConfigName("Standard WSSecurity Client"); This doesn't work as the 'port' object cannot be casted to a StubExt. I have generated my client code using the '-extensions' flag, could this be causing problems?Dos anyone have any idea as to what could be causing this problem?Thanks in advance,Tim 18396Views Tags: none (add) This content has been marked as final. Show 13 replies 1. Re: Jboss ws-security, client configuration Tim de Jager May 17, 2010 6:23 PM (in response to Tim de Jager) Alright I have gotten a bit further. I fixed the class casting issue , but I'm now getting an exception:javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: An internal WS-Security error occurred.Can't find anything in the logs though.This is the code I am using for setting up the security on the client: URL securityURL = Main.class.getResource("META-INF/jboss-wsse-client.xml"); ((StubExt) port).setSecurityConfig(securityURL.toExternalForm()); ((StubExt) port).setConfigName("Standard WSSecurity Client", "META-INF/standard-jaxws-client-config.xml"); This is the wsse-client file I'm using:
the discussion"building a WS Client with WS-Security"To view the discussion, visit: http://community.jboss.org/message/548245#548245--------------------------------------------------------------Hi all,I' am trying to build a web service client and sing the soap message.I 'am using jbossws-cxf to generate the Stubs with wsconsume tool.My first https://developer.jboss.org/thread/152040 problem is to build the jboss-wsse-client.xml ...I have my private key, my sing cert and the CA root for the server (I havent access to the server)to build a keystore I http://jboss-user.narkive.com/errcGba0/jboss-web-services-building-a-ws-client-with-ws-security use:openssl pkcs12 -export -chain -in mySing.crt -CAfile root.cer -inkey myPrivate.key -out keystore.pkcs12(I made a client with a soapui tool, and the keystore works fine)so ... my jboss-wsse-client.xml:*
colo-br-02 ! atl ! jboss ! http://wiki.servicenow.com/index.php?title=Inbound_SOAP_Web_Service_Security com [Download message RAW] Hi all, I am using Jboss Web services and WS security. I have Jboss version 4.2.2 GA. My web \ service is an internal implemented as a stateless EJB. The problem is when I invoke the web \ service from a client application, the following exception is thrown: | \ javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: An \ internal WS-Security error occurred. an internal ws-security See log for details | \ org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChai \ nExecutor.java:276) | \ org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecuto \ r.java:155) | org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(Cli \ entImpl.java:168) | org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363) | org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) | org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | $Proxy119.getUserDetailsFromURSID(Unknown Source) | test.filter.base.SecurityFilter.getUserDetails(SecurityFilter.java:274) | test.filter.base.SecurityFilter.doFilter(SecurityFilter.java:166) | org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96 \ ) | | root cause | | org.jboss.ws.core.CommonSOAPFaultException: An internal WS-Security error \ occurred. See log for details | \ org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatc \ her.java:105) | org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound( \ WSSecurityDispatcher.java:177) | \ org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecur \ ityHandler.java:78) | \ org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurit \ yHandlerClient.java:40) | \ org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) \ | org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExec \ utor.java:295) | org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage( \ HandlerChainExecutor.java:140) | \ org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168 \ ) | org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363) | org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) | org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | org.jboss.ws
Web Services Contents 1 Overview 2 Basic Authentication 3 WS-Security 3.1 Enabling WS-Security Verification 3.1.1 Marking Service Accounts as Internal Integration Users 3.2 WS Security Profiles 3.2.1 WSS X.509 Token Profile 3.2.2 WSS Username Token Profile 3.2.3 Example WS-Security SOAP Envelope Headers 3.3 SOAP Security Policies 3.3.1 Activating the Plugin 3.3.2 Adding Certificates for Signed Requests 3.3.3 Creating a New Security Policy 3.3.4 Requiring Signed SOAP Requests 3.3.5 Specifying the Instance SOAP Security Policy 3.3.6 Installed With the Plugin 3.4 Enabling WS-Security Logging 3.4.1 WS-Security Error Messages 4 Web Service User Roles 4.1 Default Role Requirements 5 Enforcing Strict Security 6 Mutual Authentication 7 SOAP Security Example 8 Enhancements 8.1 Dublin 1 Overview ServiceNow enforces web service security using a combination of basic authentication challenge/response over the HTTP protocol and system level access control using the Contextual Security. Administrators can control what system resources web services users can access by granting them one of the SOAP roles. 2 Basic Authentication To enforce basic authentication for the user associated with the instance for each WSDL or SOAP message request, administrators can set the property glide.basicauth.required to true. When enabled, each WSDL and SOAP request must contain an "Authorization" header as specified in the Basic Authentication protocol. Because web services requests are non-interactive, ServiceNow always requires the Authorization header during a request. Note: Basic Authentication refers to local credentials or LDAP authentication, if configured. Supplying basic authentication information with every request (whether or not it is required) has the added advantage that ServiceNow can associate Web Service invocations with the user supplied in the basic authentication credentials. For example, when creating an Incident record, the journal fields lists the user ID contained in the basic authentication header instead of the default Guest user. View code samples To s