Basic authentication in header soap message

Author: afz_guc@rdv25772.dds.nl (rdv25772)

Hello everyone,   For a customer I need to add basic authentication in the header of a soap message, not in the message self. I have been searching in the help of Uniface and on the web. Neither sources states information on how to solve it. What I can find is about SMTP handling. I want to do the handling with Uniface and not with other programmes. At the moment Uniface 9.6 is used. In the near future a migration to Uniface 9.7(.04) will take place. At this moment it is expected that the required change will be done in 9.7, but this is a decision to be made. Can anyone set me to the right direction? Regards,   Richard

3 Comments

  1. What kind of authentication? Is it user and password? They should be available using SOP_PARAMS (euser,epass), you can also set these in the [SERVICES_EXEC] part of the asn (e.g. SOP_SVC=$SOP:SOP_SVC euser=fred epass=Pa55w0rd) and I believe, in later versions of 9.7 by using $signatureproperties from within proc.   

    SOAP Connector Options

    You can set the default SOAP connector options using the USYS$SOP_PARAMS setting in the [DRIVER_SETTINGS] section of the assignment file. They can be overridden for specific components in the [SERVICES_EXEC] section. and they can be set dynamically using the $signatureproperties Proc function.

    USYS$SOP_PARAMS {=} {puser=ProxyServerUserID} %\     {ppass=ProxyServerPassword} %\     {euser=WebServerUserID} %\     {epass=WebServerPassword} %\     {scheme=AuthScheme} %\     {proxy=ProxySpec} %\     {cto=ConnectionTimeOut} %\     {rto=RequestTimeOut} %\     {ign=IgnoredVerificationMethod}  %\     {callback=CallbackServices} %\     {wsdl=Location} %\     {svc=EndpointURI}


    Author: Iain Sharp (i.sharp@pcisystems.co.uk)
  2. Yes Iain, it is an username and password combination. At the moment it will be implemented for only one soap message. The customer wants to implement a higher level of security on all programmes it is using. At the moment  we don't use signature and so to build the soap messages. We use different kinds of methods to do so. Due to a lack of knowledge about the subject, we have not migrated to the preferred solution of Uniface and the SOP 2.0 connector.   Regards,   Richard


    Author: rdv25772 (afz_guc@rdv25772.dds.nl)
  3. I have found the SOP 2.0 connector to be very useful for consuming (and providing) web-services. It's obviously a bit old fashioned and limited for multi part messages.  Using /sti against the wsdl generally provides me with the correct signature relatively easily and from there it's all built in. 


    Author: Iain Sharp (i.sharp@pcisystems.co.uk)