setHeader in Web Service Consumer (Java)

hcl-bot · October 7, 2010, 1:42pm

I am trying to create a web service consumer on Notes 8.5.2. I am trying to add authentication headers (username and password), but the Stub setHeader method “is not visible” according to the DDE message. Sure enough, when I try to use the type-ahead, lotus.domino.axis.client.Stub does not seem to have a setHeader method.

What am I missing? How can I set the head in 8.5.2?

It worked on 7.0.3 using Stubby. (Had a different problem there with the service call parameter being sent in the header instead of the body, which I am hoping 8.5.2 will solve).

I’ve searched this forum and all over the web, but have been unable to find a solution. Any help would greatly appreciated.

—begin code—

import lotus.domino.*;

import Request_Management.*;

import javax.xml.soap.*;

import lotus.domino.axis.client.Stub;

import lotus.domino.axis.message.SOAPHeaderElement;

public class JavaAgent extends AgentBase {

public void NotesMain() {



  try {

      Session session = getSession();

      AgentContext agentContext = session.getAgentContext();



      // (Your code goes here)

      Request_ManagementServiceLocator locator = new Request_ManagementServiceLocator();

      Request_ManagementPortType service = locator.getRequest_ManagementSoap();

      Stub ws;

      SOAPHeaderElement oHeaderElement; 

      SOAPElement oElement;

      

      lotus.domino.axis.client.Stub s = (lotus.domino.axis.client.Stub) service;

		SOAPHeaderElement header = new SOAPHeaderElement("urn:AuthenticationInfo", "AuthenticationInfo");

		SOAPElement node = header.addChildElement("userName");

		node.addTextNode("User Name");

		SOAPElement node2 = header.addChildElement("password");

		node2.addTextNode("password123");

		s.setHeader(header);  //this is where it tells me "not visible"

                           

      String reqID = "R2:000000001234";

      String res = service.opGet(reqID).getRequestor();

      System.out.println(res);



  } catch(Exception e) {

      e.printStackTrace();

   }

}

—end code—

hcl-bot · February 21, 2011, 11:10pm

Subject: setHeader in Web Service Consumer (Java)

Hi Dennis,

You may well have solve this already. None the less I have managed to achieve this by manually building WSSE security tag and adding it to the SOAP header. I did this by:

Adding a method ‘getSOAPHeaderSecurity’ to the java file that contains the SOAP operation calls for the webservice (generated from the wsdl)
modifying each SOAP operation call to add the security info to the header using the method above. eg _call.addSOAPHeader(getSOAPHeaderSecurity())

;

I used the method ‘setCredentials(userName, password)’ in the webservice object (stub) to pass the credientials to the getSOAPHeaderSecurity method mentioned above(so i didn’t have to hardcode this).

Here’s the code for the method I added:

private SOAPHeaderElement getSOAPHeaderSecurity(){

	try{

	//Example of what we are adding to the header

    	//<soapenv:Header>

    	//	<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

    	//		<wsse:UsernameToken wsu:Id="UsernameToken-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

    	//			<wsse:Username>SOMEUSERNAME</wsse:Username>

    	//			<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password>

    	//			<wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MECGjqTmLEfyl/ZYkNe9Eg==</wsse:Nonce>

    	//			<wsu:Created>2010-10-01T07:20:28.769Z</wsu:Created>

    	//		</wsse:UsernameToken>

    	//	</wsse:Security>

    	//</soapenv:Header>



    	final PrefixedQName qname = new PrefixedQName("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd", "Security", "wsse");

    	final SOAPHeaderElement security = new SOAPHeaderElement(qname);

    	security.setMustUnderstand(true);

        

        final SOAPElement usernameToken = security.addChildElement("UsernameToken", "wsse");

        usernameToken.setAttribute("wsu:Id","UsernameToken-1");

        usernameToken.addNamespaceDeclaration("wsu", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd");

        

	//Create the username node and get the value from the stub which we set before we called the web service

        final SOAPElement username = usernameToken.addChildElement("Username", "wsse");

        username.addTextNode(this.getUsername());

        

	//Create the password node and get the value from the stub which we set before we called the web service

        final SOAPElement password = usernameToken.addChildElement("Password", "wsse");

        password.setAttribute("Type", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText");

        password.addTextNode(this.getPassword());

                    

        return security;

    	

    }catch (final Exception e){

    	e.printStackTrace();

    }

	return null;

    

}

Here’s an example of the modified call using the above method to add the athentication header:

public com.XXX.WebServices.ssl.Data._2010._10.ApprovalDelegationResponse getApprovalDelegationStatus(com.XXX.schemas.WebServices.ssl.Data._2010._10.ApprovalDelegationRequest request) throws java.rmi.RemoteException {

    lotus.domino.websvc.client.Call _call = createCall("getApprovalDelegationStatus");

    _call.addHeader(getSOAPHeaderSecurity()); // <<=== JUST ADD THIS LINE TO ANY WEBSERVICE OPERATION CALL TO INSERT WSSE SECURITY INFOR MATION

    java.lang.Object _resp = _call.invoke(new java.lang.Object[] {request});

    return (com.XXX.schemas.WebServices.ssl.Data._2010._10.ApprovalDelegationResponse) _call.convert(_resp, com.XXX.schemas.WebServices.ssl.Data._2010._10.ApprovalDelegationResponse.class);

}

In the agent calling the webservice I passe the credentials from configuration documents as follows:

		UserService_Port stub = new UserService_ServiceLocator().getBasicHttpBinding_UserService(new java.net.URL(tmpdoc.getItemValueString("Value")));

		username = vwConfig.getDocumentByKey("SERVICE_USERNAME", true).getItemValueString("Value");

		password = vwConfig.getDocumentByKey("SERVICE_PASSWORD", true).getItemValueString("Value");

		stub.setCredentials(username, password); //<< THESE PROPERTIES ARE READ WHEN CREATING THE SECURITY NODE IN THE SOAP HEADER.

…Make your service call

This all works for basic authentication.

The journey to get that sorted out was a long one. I have another complication at the moment with trying to consume a web service through a proxy server which requires authentication - what a headache. IBM has to do much better with its documentaion on such matters! I will post anothor question on that and hope that some else has solved that issue.

Hope this helps you out.

Regards

Sean