CMIS for Documentum - Authentication

Hello group

I am using Documentum for quite some time and have expirience in using DFS. As I need to move on the project where I will use CMIS, I have question about it. I downloaded and deployed CMIS on my tomcat (I followed deployment instructions from deployment guide). I am able to see wsdl, everything seem to work fine. I have referenced CMIS web service (ObjectService) into my sample C# application and that was also ok. Now I need info, how to autheticate to my docbase. I have written following code:

CMIS.

ObjectServicePort objectService = new CMIS.ObjectServicePortClient();CMIS.

createDocumentRequest request = new CMIS.createDocumentRequest();request.folderId =

"0c00000f80000107"; // ID of temp cabinetrequest.contentStream =

new CMIS.cmisContentStreamType() { filename = "c:\\Test.txt" };request.properties =

new CMIS.cmisPropertiesType();request.properties.Items =

new CMIS.cmisProperty[] { new CMIS.cmisPropertyString() { propertyDefinitionId = "object_name", localName = "object_name", displayName = "Object Name", value = new string[] { "Test" } } };request.repositoryId=

"playground";request.versioningState = CMIS.

enumVersioningState.major;objectService.createDocument(request);

When I start this I get:

System.ServiceModel.FaultException`1 was unhandled
Message=Authentication failed due to missing credentials
[com.emc.documentum.fs.cmis.impl.dfs.exception.AuthenticationException] null

So, how I create and pass credentials to CMIS service?

Thanks

Find more posts tagged with

Documentum

Comments

abc123

For SOAP binding CMIS services, we support WS UsernameToken security header in EA releases; And for AtomPub binding CMIS services, we support HTTP Basic authentication.

- William

ingbabic

Thank you Zhou

Can you please provide a code sample, how do we do it? I am using .NET client.

abc123

I don't have .NET env to supply a code somple for you. But just like common WCF service, you can write a SOAP header on the SOAP request message, including your Documentum credential. Here is a sample SOAP header.

<S:Header>
 <wsse:Security S:mustUnderstand="1">
 <wsse:UsernameToken       xmlns:ns15="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity"       xmlns:ns14="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512"       xmlns:ns13="http://www.w3.org/2003/05/soap-envelope"       wsu:Id="XWSSGID-1281943163394-1251403611">
         <wsse:Username>documentum_user</wsse:Username>         <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">               plain_password         </wsse:Password>
 </wsse:UsernameToken>
 </wsse:Security>
 </S:Header>

ingbabic

Do you have sample in Java? It would really be nice if you can provide one, since I didn't saw anywhere even minimal sample. Can be quick and dirty, just as a starter...

Thanks

Sasa

ingbabic

Ok, I have found a way to accomplish authentication thanks to Craig's blog about it. Now when I try to getContentStream from ObjectService it succeeds on smaller files, but if I try to download anything above 40 K (or so) I get exception:

System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

Funny enough it is not a problem to create document with a content stream of quite large size (above 600k for example).

I tried to increase MaxReceivedMessageSize in ObjectServicePortBinding in my app.config. but no matter which number I put there I allways get same message (as if I have never changed app.config). What can be the cause?

abc123

Make sure ObjectServicePortBinding is the correct binding where the max message size error occured and the ObjectServicePortBinding is activated for your ObjectService endpoint.

You can try to remove the service reference and try to add it again.

Set both maxBufferSize and maxReceivedMessageSize with a valid number. The max number is 2147483647.

- Regards,

William

ingbabic

I have finally succeed in retrieving larger files but using possibility of getContentStream method to specify chunk size and ofset and the reading in loop. However it doesn't matter if I specify both maxBufferSize and maxReceivedMessageSize (I even changed maxBytesPerRead property in app.config) it can't read more then about 40000 bytes per read.

satish.malluvalasa

i am getting same exception

my code is

CmisRepositoryCapabilitiesType capabilitiesType=new CmisRepositoryCapabilitiesType();
        System.out.println("capabilities - "+capabilitiesType.getAny());
        URL url=new URL("http://localhost:8080/emc-cmis-ea/services/RepositoryService?wsdl");
        QName qName=new QName("http://docs.oasis-open.org/ns/cmis/ws/200908/", "RepositoryService");
        RepositoryService service = new RepositoryService(url, qName);

        System.out.println("User - "+service.getWSDLDocumentLocation().getUserInfo());
        System.out.println("Path - "+service.getWSDLDocumentLocation().getPath());
        System.out.println("local part - "+service.getServiceName().getLocalPart());


        CmisExtensionType ext=new CmisExtensionType();
        System.out.println("ext type - "+ext.getAny());
       System.out.println(service.getRepositoryServicePort().getRepositoryInfo("3c0dca3480000103",ext));

plz help how to write soap header.

deve_adp

Hi,

I am using CMIS sample code available on Craig's blog to accomplish authentication to a CMIS, where I am receiving the below error....

The header 'Security' from the namespace 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding.

Please help me to resolve this error..

Thanks in advance.

fmui

You might want to have a look at Apache Chemistry DotCMIS [1].

Even if you want to use it, it has the code that solves the problems mentioned in this thread.

Florian

[1] http://chemistry.apache.org/dotnet/dotcmis.html