C++ client for DFS Services

We are developing C++ client for DFS services. We are using

gSOAP tool to create proxy for DFS services. We have created a proxy for

ContextRegistryService and successfully getting servicetoken string through ContextRegistryService.

In the .Net Sample (DfsDotNetSample) they were using WSE 3.0

to create the SecurityToken and embed it with QueryService to pass the token. Same

thing we have to implement in C++. But we don’t have support to include WSE

3.0. Is there a way to implement this without WSE.

Thanks in advance

Rafi

Find more posts tagged with

Comments

craigrandall

The current DFS SDK (i.e. version 6.5) contains samples for both Java clients and C# clients. Currently there are no C++ client samples in the SDK. However, gSOAP should be able to proxy all DFS services, and you've indicated success in that regard already.

BTW, .NET support is now based on Windows Communication Foundation (WCF) "v1" in .NET 3.0. WCF supersedes WSE 3.0, and WSE 3.0 is no longer supported by DFS (since 6.0 SP1).

Thanks for your reply. Between I am partially

successful in creating C++ client. If I set the connection type ‘anonymous’ instead

of ‘authorized’ DFS CPP client works for me. gSOAP has a plug-in for wsse which

is equivalent to WSE framework for Windows. I am not successful in using the

wsse plugin with gSOAP which will make the connection ‘authorized’.

Thanks,

Rafi

craigrandall

OK. It sounds like the focus is now upon passing a valid ServiceContext header in your SOAP request message via gSOAP. (WS-Security is involved in subsequent requests by virtual of the BinarySecurityToken returned by the DFS runtime Context Registry service. So, I don't think the current focus is on WSSE/gSOAP coding.)

Although my post is focused on C# (.NET), I think that you'll find it useful here, too: http://craigrandall.net/archives/2008/07/dfs-object-service-consumer-2b/http://craigrandall.net/archives/2008/07/dfs-object-service-consumer-2b/. It talks about how to setup a valid ServiceContext header.

It shouldn't be too difficult to translate the C# sample code into C++/gSOAP code. If this does prove to be too much to ask, please let me know what version of gSOAP that you're using? Providing code, when possible, is always helpful, too...

To include the ServiceContext in the soap request header, following

should be added to the header file generated from wsdl2h

struct SOAP_ENV__Header

{

ns10__ServiceContext* ns10__ServiceContext_ ;

///< SOAP Header element

""http://context.core.datamodel.fs.documentum.emc.com/":ServiceContext"

part "header"

};

I included the valid ServiceContext in the soap header again the same

problem exists. Following is the request which is equals to the c# generated

SOAP request

<SOAP-ENV:Header>

<ns10:ServiceContext>

*<ns10:Identities

xsi:type="ns10:RepositoryIdentity" password="[password]"

userName="[username]" repositoryName="[repositoryname]">*

</ns10:Identities>

</ns10:ServiceContext>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<ns6:execute>

*<query

xsi:type="ns3:PassthroughQuery" queryString="select object_name

from dm_document">*

*<ns3:repositories>[repository

name]</ns3:repositories>*

</query>

*<execution

maxResultPerSource="0" maxResultCount="0"

startingIndex="0"></execution>*

</ns6:execute>

</SOAP-ENV:Body>

But this is not only the case. Every time sending the username, password

with soap header will be an issue. I think making it authorized using token will be

best way. For more, BinarySecurityToken is available in wsse plugin of gSOAP.

Thanks,

Rafi

craigrandall

Although I see your declaration of "ns10", I don't see the namespace in the SOAP request message.

In my C# example online, the SOAP request message is as follows:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<ServiceContext xmlns="http://context.core.datamodel.fs.documentum.emc.com/">
<Identities xsi:type="RepositoryIdentity" userName="_USER_" password="_PWD_" repositoryName="_DOCBASE_" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ServiceContext>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> . . . </s:Body>
</s:Envelope>

Do you have your XML namespacing set up correctly in gSOAP to match the above, valid message example? How does a DFS service know how to resolve, for example, SOAP-ENV:Header?

Previously I sent only request header and body. Now following is the full SOAP request generated from gsoap CPP client

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://schema.core.datamodel.fs.documentum.emc.com/" xmlns:ns3="http://qu

ery.core.datamodel.fs.documentum.emc.com/" xmlns:ns5="http://profiles.core.datamodel.fs.documentum.emc.com/" xmlns:ns8="http://content.core.datamodel.fs.documentum.emc.com/" xmlns:ns7="http://core.datamodel.fs.documentum.emc.com/" xmlns:ns4

="http://properties.core.datamodel.fs.documentum.emc.com/" xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open

.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:ns2="http://rt.fs.documentum.emc.com/" xmlns:ns10="http://context.core.datamodel.fs.documentum.emc.com/" xmlns:ns6="http://cor

e.services.fs.documentum.emc.com/" xmlns:ns9="http://services.rt.fs.documentum.emc.com/">

<SOAP-ENV:Header>

<ns10:ServiceContext>

<ns10:Identities xsi:type="ns10:RepositoryIdentity" password="password" userName="username" repositoryName="repository">

</ns10:Identities>

</ns10:ServiceContext>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<ns6:execute>

<ns3:repositories>Repository</ns3:repositories>

</query>

</execution>

</ns6:execute>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Here you can see the XML namespace mapping in the ENVELOPE tag.

Thanks,

Rafi