This content has been marked as final.
Show 5 replies
-
1. Re: Can a DII client access a WSDL locked down by basic HTTP
nehring Oct 29, 2005 1:11 PM (in response to csnow)Been awhile since using DII. Have you tried setting the USERNAME_PROPERTY and PASSWORD_PROPERTY on the Call object?
-
2. Re: Can a DII client access a WSDL locked down by basic HTTP
nehring Oct 29, 2005 1:35 PM (in response to csnow)Sorry, just noticed that you were talking about accessing the WSDL. Maybe a URL with the user/password specified in it would work.
Something like:http://user:password@server/webservice?wsdl
Not sure if this will actually work, plus it limits the characters allowed for the password. -
3. Re: Can a DII client access a WSDL locked down by basic HTTP
csnow Oct 29, 2005 2:50 PM (in response to csnow)That is a great idea but unfortunately I tried that and it didn't work. Now, if I do that from firefox it works fine but I think the client has to support such a feature. Here is my relevant client code:
ServiceFactoryImpl factory = (ServiceFactoryImpl)ServiceFactory.newInstance(); URL wsdlURL = new URL(WSDL_LOCATION); QName serviceName = new QName(NAMESPACE, SERVICE_NAME); Service service = factory.createService(wsdlURL, new URL(JAX_RPC_MAPPING_LOCATION), null, serviceName, PORT_NAME);
-
4. Re: Can a DII client access a WSDL locked down by basic HTTP
thomas.diesler Nov 2, 2005 3:46 AM (in response to csnow)This has been assigned to
http://jira.jboss.com/jira/browse/JBWS-483 -
5. Re: Can a DII client access a WSDL locked down by basic HTTP
wejaeger Nov 5, 2005 8:59 AM (in response to csnow)I had the same problem. I solved it by using a java.net.Authenticator implementation.
class AuthImpl extends java.net.Authenticator { ... PasswordAuthentication getPasswordAuthentication() { return your credentials here } ... }
Before you read the WSDL do something like thisAuthenticator.setDefault(new AuthImpl(...));
At least in my case it worked.