September 2009 - jbossws-users - Jboss List Archives

[JBoss Web Services Users] - Exception with X509 certificates on jbossws-native-3.1.1.GA

by jorgerst

Hi! I'm having trouble to use WS-Security with X509 certificates. I've followed the instructions of the wiki ( http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide#WSSecurity ). But when I invoke my service (using SoapUI, correctly configured with a X509 signed and encrypted SOAP request) I am getting the following exception: ERROR [WSSecurityDispatcher] Internal error occured handling inbound message: | org.jboss.ws.extensions.security.exception.WSSecurityException: Currently only SubjectKeyIdentifiers are supported, was passed: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil... Plus, my jboss-wsse-server.xml is like this: | <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/ws-security/config jboss-wsse-server.xsd"> | | <key-store-file>WEB-INF/wsse.keystore</key-store-file> | <key-store-password>jbossws</key-store-password> | <trust-store-file>WEB-INF/wsse.truststore</trust-store-file> | <trust-store-password>jbossws</trust-store-password> | | <config> | <encrypt type="x509v3" alias="wsse" /> | <sign type="x509v3" alias="wsse" /> | <requires> | <encryption /> | <signature /> | </requires> | <timestamp ttl="300" /> | </config> | </jboss-ws-security> I'm using Sun JDK 1.5.0.15, JBoss AS 4.2.3 and jbossws-native-3.1.1.GA. I'm not very familiar with the security stuff, so please, if anybody could help it will be great! Thanks in advance! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257143#4257143 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257143

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Authenticating SOAP Requests with WSSE UsernameToken does no

by sthatcher

I have created a simple EJB3 project and exposed it as a web service (your typical Echo service). I'm using WSSE UsernameToken headers in the SOAP requests to send authentication info. I can successfully authenticate using a username and digesting the password (e.g. Base64 encode of the SHA-1 hash). However, when I encorporate the Created node and add to the digest I get an "Invalid User" exception. But, I can use just the hash of the password (without the created node) and authenticate successfully. According to the docs from the OASIS site the digest is computed as (taken from Web Services Security UsernameToken Profile): | Password_Digest = Base64 ( SHA-1 ( nonce + created + password ) ) | I'm currently not using a Nonce since the spec says that both the Nonce and the Created are optional. It's as if the server is ignoring the fact that the created node exists. I'm not fully confident that I have the jboss-wsse-server.xml file set up or even the security header. See below for the appropriate files. Any thoughts would be appreciated. EJB3 Service: | package com.test; | | import javax.annotation.security.RolesAllowed; | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebParam; | import javax.jws.WebResult; | import javax.jws.WebService; | | import org.jboss.ws.annotation.EndpointConfig; | | @Stateless | @WebService(endpointInterface = "com.test.IEchoSession", serviceName="EchoService", portName="EchoServiceSOAP") | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | public class EchoSession implements IEchoSession { | | /** | * | */ | private static final long serialVersionUID = 1L; | | @Override | @WebMethod(operationName="Echo") | @WebResult(partName="EchoResponse") | @RolesAllowed(value={"friend"}) | public String echo(@WebParam(partName="text") String text) { | return "You said: " + text; | } | | } | jboss.xml (in the EJB3 META-INF folder): <?xml version="1.0" encoding="utf-8"?> | <jboss> | <security-domain>java:/jaas/MyRealm</security-domain> | <webservices> | <context-root>/echo</context-root> | </webservices> | <enterprise-beans> | <session> | <ejb-name>EchoSession</ejb-name> | <port-component> | <port-component-name>EchoSession</port-component-name> | <port-component-uri>/EchoService</port-component-uri> | <transport-guarantee>NONE</transport-guarantee> | <secure-wsdl-access>false</secure-wsdl-access> | </port-component> | </session> | </enterprise-beans> | | </jboss> jboss-wsse-server.xml (also in the META-INF): <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/ws-security/config | http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> | <config> | <username/> | <timestamp ttl="300"/> | <timestamp-verification createdTolerance="100" warnCreated="false" expiresTolerance="100" warnExpires="false" /> | <authenticate> | <usernameAuth/> | </authenticate> | </config> | </jboss-ws-security> | On the client side (flex component) the following header get's added to the request: | private function addWSSEHeader(): SOAPHeader { | | var date : Date = new Date(); | _ds = getDateString(date); | date.minutes += 3; | | var plain : String = SHA1.hashToBase64(password.text); | | _password = SHA1.hashToBase64(_ds + password.text); | | trace("plain: " + plain); | trace("timestamp " + _password); | var usernameTokenXML:XML = | <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..." | xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..."> | <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..."> | <wsu:Created>{_ds}</wsu:Created> | <wsu:Expires>{getDateString(date)}</wsu:Expires> | </wsu:Timestamp> | <wsse:UsernameToken> | <wsse:Username Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...">{username.text}</wsse:Username> | <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr..." | xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...">{_password}</wsse:Password> | <wsu:Created>{_ds}</wsu:Created> | </wsse:UsernameToken> | </wsse:Security> | | var wsse: Namespace = new Namespace("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..."); | var wsseSecurity: QName = new QName(wsse.uri, "Security"); | var header: SOAPHeader = new SOAPHeader(wsseSecurity, {"wsse":"Security"}); | header.content = usernameTokenXML; | | return header; | } | | And here is an example of the SOAP message: | <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><SOAP-ENV:Header><wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit...'> | <wsu:Timestamp> | <wsu:Created>2009-09-25T13:07:29Z</wsu:Created> | <wsu:Expires>2009-09-25T13:10:29Z</wsu:Expires> | </wsu:Timestamp> | <wsse:UsernameToken> | <wsse:Username Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...'>kermit</wsse:Username> | <wsse:Password Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr...'>lKnNIypKvfb27kzvQynQtS+iNUc=</wsse:Password> | <wsu:Created>2009-09-25T13:07:29Z</wsu:Created> | </wsse:UsernameToken> | </wsse:Security></SOAP-ENV:Header><SOAP-ENV:Body> | <tns:echo xmlns:tns='http://test.com/'> | <arg0>test</arg0> | </tns:echo> | </SOAP-ENV:Body></SOAP-ENV:Envelope> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257096#4257096 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257096

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: avoid lazy-initialization exceptions

by lespoches

I think the solution is to use @XmlAccessorFactory on Entity Bean and override default accessor ! But by default, Jboss do not exploit this annotation when creating JAXBContext and i can't find how to enable this Binding customization. If anyone have an idea, help would be greatly appreciated Jo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257095#4257095 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257095

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: Intermittent failures in multithreaded test

by adinn

Hi Alessio, I will try it as soon as I can. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257067#4257067 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257067

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - WSDL 2.0 supported?

by Oberiko

Hello, This likely seems like an obvious question, but both Google and the search on these forums is turning up almost nothing. Does JBossWS (native) support WSDL 2.0? If so, are there any drawbacks to using it (i.e., can't use WS-RM or anything). Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256964#4256964 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256964

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: Cannot Access Secure EJB3 Web Service

by skerstetter

here is the unit test failure: | request requires HTTP authentication: Unauthorized; nested exception is: request requires HTTP authentication: Unauthorized View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256906#4256906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256906

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Cannot Access Secure EJB3 Web Service

by skerstetter

I have a web service that worked fine in AS 4.2.1GA, but since porting to 5.1.0GA, I have been unable to access it if it is secure. If I remove authMethod=BASIC setting of the WebContext, I can access the ejb, but it is not secure. I am using the native stack, version 3.2.0GA. Here is my interface definition (simplified): | @WebService | @SOAPBinding(style = SOAPBinding.Style.RPC) | public interface Inquiry { | | String echo(@WebParam(name="echoText", mode=Mode.IN) String echoText); | Here is my EJB3 definition: | @WebService(endpointInterface="com.foo.Inquiry") | @WebContext(contextRoot="check-inquiry", /* SEK TODO: not working */ authMethod="BASIC" /**/, secureWSDLAccess=false) | @Stateless | @SecurityDomain("my-security-domain") | @TransactionAttribute(TransactionAttributeType.SUPPORTS) //we do not require a transaction. we do not perform any updates. | @Interceptors({PerformanceProfiler.class, ExceptionLogger.class}) | public class InquiryImpl extends BasePersistentContextHolder implements Inquiry { | | @Override | public String echo(final String echoText) { | getLog().debug("echo=[" + echoText+ "]"); | return echoText; | } | Here is my jax-rpc client code: | private Inquiry getService(final String username, final String password, final boolean withAuth) throws MalformedURLException, ServiceException { | Stub stub = (Stub) new InquiryService_Impl().getInquiryPort(); | stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:8080/check-inquiry/InquiryImpl?wsdl"); | | | if (withAuth) { | stub._setProperty(javax.xml.rpc.Stub.USERNAME_PROPERTY, username); | stub._setProperty(javax.xml.rpc.Stub.PASSWORD_PROPERTY, password); | } | | return (Inquiry) stub; | } | Let's see, I've got the custom security domain configured in conf/login-config.xml. I've read through the documentation and tried a number of things with other configuration files, like jboss-wsse-server.xml in META-INF. Nothing has worked. I am deploying as an ejb-jar file inside of an ear file. I'm hoping that someone can see some inconsistency in this all that I have missed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256905#4256905 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256905

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: Error when calling web service within JBoss

by PeterJ

How are you starting the app server? Are you using the -b option and if so what hostname/IP address are you passing? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256901#4256901 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256901

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: error when using wsgen to generet wsdl

by Josief

<target name="build-server-java" description="Generate the WSDL files for the webservices" depends="compile"> | <taskdef name="wsgen" classname="com.sun.tools.ws.ant.WsGen"> | <classpath refid="build.classpath" /> | </taskdef> | <wsgen genwsdl="true" keep="true" verbose="true" destdir="${wsdl.dir}" sei="yourPackage.YourClass"> | <classpath> | <pathelement path="${lib.dir}/ejb-api.jar"/> | <pathelement path="${lib.dir}/jboss-seam.jar"/> | <path location="${jar.dir}" /> | </classpath> | </wsgen> | </target> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256799#4256799 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256799

15 years, 3 months

1
0
0 / 0

[JBoss Web Services Users] - Re: error when using wsgen to generet wsdl

by Josief

The topic was sleeping but I had the same issue and I found this solution, using wsgen as an ant task: The problem was the classpath. This is my wsgen task: View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256797#4256797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256797

15 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users September 2009