Perhaps if you were to serialize the call object and store it in a cookie, you
could then retrieve it from the cookie and deserialize it to be used again. In
this way, it would still have the user authentication set and would only need
to be changed based on the service call that you wanted to make. I don't know
if that makes any sense or if it would even work, but that is where I would
start. If it does work, you could even substitute a http session object for
the cookie.
Pobzeb Armerding
Vann's Inc.
Software Engineer
On Wed, 02 Nov 2005 12:48:46 -0800, Ravi Krishnamurthy wrote:
| Thanks Pobzeb.
|
| Also I have one more question as a followup. I will try to explain
| the requirement to the best of my ability below:
|
| IN single sign on situation, the user has already logged into a
| server and then if a webservice call happens, I want to use that
| already authorized ID. IN other words I would like to store cookies
| to be used in the webservice invocation. WOndering how this can be
| done using the Call objects.
|
| Thanks,
| Ravi
|
| Pobzeb Armerding wrote:
|
|| I have actually just finished a webservice client that uses the
|| setUsername and setPassword methods of the call interface. This
|| is how it works:
||
|| SOAPInterface_PortType service = new
|| SOAPInterfaceLocator().getSOAPInterface();
|| ((SOAPInterface_BindingStub)service).setUsername("username");
|| ((SOAPInterface_BindingStub)service).setPassword("password");
||
|| SOAPReturn return = service.getMethod(Parameters);
||
||
|| The only issue that I found with this method is that the password
|| needed to be encrypted for my use. If I did not encrypt the
|| string used in the password, I received a 401 Authentication
|| error.
||
|| I hope this helps you to at least get started.
||
|| Pobzeb Armerding
|| Vann's Inc.
|| Software Engineer
||
|| On Mon, 31 Oct 2005 15:42:34 -0800, Ravi Krishnamurthy wrote:
||
||| Hello:
||| I see the call interface has setUserName and setPassword.
||| Wondering if there is any example on how to set up a webservice
||| that needs the username and password for testing.
|||
||| Thanks,
||| Ravi
