Net Express 5.1: Username & password in client generated using wsdl-file

[Migrated content. Thread originally posted on 21 June 2011]

Compared to Net Express 5.0 the generated proxy now supports a username and a password parameter, unrelated to the supplied wsdl. What use can be made of these parameters?

The username/password is used for HTTP basic authentication where required by your web server.

[Migrated content. Thread originally posted on 21 June 2011]

Compared to Net Express 5.0 the generated proxy now supports a username and a password parameter, unrelated to the supplied wsdl. What use can be made of these parameters?

Hi Chris,

i am trying to make use of exactly this functionality and invoke a remote WS, but I get the following messages:
(this is the output of the Net Express generated program by using the WSDL provided)

Service Address (Enter = www1.gsis.gr/.../RvWsAfeSoappHttpPort): Username optional):RvWsAfe
Password (optional): RvWsAfe1
Operation (1 = rvWsAfeIssue, 2 = rvWsAfeValidation, 3 = rvWsAfeVersionInfo): 3
faultcode: InvalidSecurity
faultstring: Missing in SOAP Header


Although I type a user name and password, it seems that they don't get to the server. Am I doing somehting wrong here?


regards
Panos

[Migrated content. Thread originally posted on 21 June 2011]

Compared to Net Express 5.0 the generated proxy now supports a username and a password parameter, unrelated to the supplied wsdl. What use can be made of these parameters?

The error message that you are receiving says “Missing in SOAP Header”, which would indicate an error completely separate from the basic authentication.

This error indicates that you are trying to use WS-Security on your Web Server and that this isn't supported in the generated client.

Can you confirm that the web service that you are trying to call is expecting WS-Security in the SOAP message?

[Migrated content. Thread originally posted on 21 June 2011]

Compared to Net Express 5.0 the generated proxy now supports a username and a password parameter, unrelated to the supplied wsdl. What use can be made of these parameters?

Hi Chris,

Unfortunately, i am not an expert in Web Services and i cannot tell about the security. I have asked the vendor to provide this information.

All I have is the wsdl that i used to create the Net Express client which gives the error. I include it below in case you can see something:

<pre>
<?xml version="1.0" encoding="UTF-8" ?>
<definitions xmlns="schemas.xmlsoap.org/.../" xmlns:tns0="gr/.../" xmlns:soap12="schemas.xmlsoap.org/.../" xmlns:soap="schemas.xmlsoap.org/.../" xmlns:xsd="www.w3.org/.../XMLSchema" xmlns:mime="schemas.xmlsoap.org/.../" xmlns:tns="gr/.../RvWsAfe.wsdl" name="RvWsAfe" targetNamespace="gr/.../RvWsAfe.wsdl">
<types>
<schema xmlns="www.w3.org/.../XMLSchema" xmlns:wsdl="schemas.xmlsoap.org/.../" xmlns:xsi="www.w3.org/.../XMLSchema-instance" xmlns:soap11-enc="schemas.xmlsoap.org/.../" xmlns:tns="gr/.../" targetNamespace="gr/.../" elementFormDefault="qualified">
<complexType name="RvWsAfeIssueRtUser">
<complexContent>
<extension base="tns:RvWsAfeIssueRtBase">
<sequence>
<element name="rvAfeEndDate" type="string" nillable="true" />
<element name="rvAfeAa" type="decimal" nillable="true" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="RvWsAfeIssueRtBase">
<sequence />
</complexType>
<complexType name="GenWsErrorRtUser">
<complexContent>
<extension base="tns:GenWsErrorRtBase">
<sequence>
<element name="errorDescr" type="string" nillable="true" />
<element name="errorCode" type="string" nillable="true" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="GenWsErrorRtBase">
<sequence />
</complexType>
<complexType name="RvWsAfeValidationRtUser">
<complexContent>
<extension base="tns:RvWsAfeValidationRtBase">
<sequence>
<element name="rvAfeAfm" type="string" nillable="true" />
<element name="rvAfeAa" type="decimal" nillable="true" />
<element name="rvAfeYear" type="decimal" nillable="true" />
<element name="rvAfeType" type="decimal" nillable="true" />
<element name="rvAfeDoy" type="string" nillable="true" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="RvWsAfeValidationRtBase">
<sequence />
</complexType>
</schema>
</types>
<message name="RvWsAfe_rvWsAfeIssue">
<part name="pAfeAfm" type="xsd:string" />
<part name="pAfeIssueRec_out" type="tns0:RvWsAfeIssueRtUser" />
<part name="pCallSeqId_out" type="xsd:decimal" />
<part name="pErrorRec_out" type="tns0:GenWsErrorRtUser" />
</message>
<message name="RvWsAfe_rvWsAfeIssueResponse">
<part name="pAfeIssueRec_out" type="tns0:RvWsAfeIssueRtUser" />
<part name="pCallSeqId_out" type="xsd:decimal" />
<part name="pErrorRec_out" type="tns0:GenWsErrorRtUser" />
</message>
<message name="RvWsAfe_rvWsAfeValidation">
<part name="pAfeValidationRec" type="tns0:RvWsAfeValidationRtUser" />
<part name="pAfeEndDate_out" type="xsd:string" />
<part name="pCallSeqId_out" type="xsd:decimal" />
<part name="pErrorRec_out" type="tns0:GenWsErrorRtUser" />
</message>
<message name="RvWsAfe_rvWsAfeValidationResponse">
<part name="pAfeEndDate_out" type="xsd:string" />
<part name="pCallSeqId_out" type="xsd:decimal" />
<part name="pErrorRec_out" type="tns0:GenWsErrorRtUser" />
</message>
<message name="RvWsAfe_rvWsAfeVersionInfo" />
<message name="RvWsAfe_rvWsAfeVersionInfoResponse">
<part name="result" type="xsd:string" />
</message>
<portType name="RvWsAfe">
<operation name="rvWsAfeIssue" parameterOrder="pAfeAfm pAfeIssueRec_out pCallSeqId_out pErrorRec_out">
<input message="tns:RvWsAfe_rvWsAfeIssue" />
<output message="tns:RvWsAfe_rvWsAfeIssueResponse" />
</operation>
<operation name="rvWsAfeValidation" parameterOrder="pAfeValidationRec pAfeEndDate_out pCallSeqId_out pErrorRec_out">
<input message="tns:RvWsAfe_rvWsAfeValidation" />
<output message="tns:RvWsAfe_rvWsAfeValidationResponse" />
</operation>
<operation name="rvWsAfeVersionInfo">
<input message="tns:RvWsAfe_rvWsAfeVersionInfo" />
<output message="tns:RvWsAfe_rvWsAfeVersionInfoResponse" />
</operation>
</portType>
<binding name="RvWsAfeSoapHttp" type="tns:RvWsAfe">
<soap:binding style='rpc' transport='schemas.xmlsoap.org/.../http' />
<operation name="rvWsAfeIssue">
<soap:operation soapAction="gr/.../rvWsAfeIssue" />
<input>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" parts="pAfeAfm pAfeIssueRec_out pCallSeqId_out pErrorRec_out" />
</input>
<output>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" parts="pAfeIssueRec_out pCallSeqId_out pErrorRec_out" />
</output>
</operation>
<operation name="rvWsAfeValidation">
<soap:operation soapAction="gr/.../rvWsAfeValidation" />
<input>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" parts="pAfeValidationRec pAfeEndDate_out pCallSeqId_out pErrorRec_out" />
</input>
<output>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" parts="pAfeEndDate_out pCallSeqId_out pErrorRec_out" />
</output>
</operation>
<operation name="rvWsAfeVersionInfo">
<soap:operation soapAction="gr/.../rvWsAfeVersionInfo" />
<input>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" />
</input>
<output>
<soap:body use="literal" namespace="gr/.../RvWsAfe.wsdl" parts="result" />
</output>
</operation>
</binding>
<service name="RvWsAfe">
<port name="RvWsAfeSoapHttpPort" binding="tns:RvWsAfeSoapHttp">
<soap:address location="www1.gsis.gr/.../RvWsAfeSoapHttpPort" />
</port>
</service>
</definitions>
</pre>

Thanks
Panos

[Migrated content. Thread originally posted on 21 June 2011]

Compared to Net Express 5.0 the generated proxy now supports a username and a password parameter, unrelated to the supplied wsdl. What use can be made of these parameters?

Hello,

I am reposting this question just to know if you have got any solution for HTTP basic authentication (username/password) in WSDL COBOL client generated using imtk toolkit .

I am using Enterprise developer 2.2 (eclipse) .

If not , can you please suggest alernate option to calll webservcie from cobol client having WS-Security Basic.

thanks

Anil Varma

#COBOL
#webservices
#ws-security