Craig Randall of Documentum outlines what it takes to
Consume CMIS WSDL in Visual Studio but
intentionally leaves out many important details...
For example, his quote:
you will likely want to take a more secure approach to managing user credentials.
Doesn't talk about what service-based interfaces exist to manage user credentials within Documentum or more importantly, how to
not manage user credentials across various implementations of CMIS. So, if you want to integrate Filenet and Documentum, do you have to store users in multiple places? If the answer is yes, then is this a good architecture?
Likewise, his comment:
There are other ways to "wire" WS-Security header creation and passing into applications. This particular sample takes a more subtle (less in-your-face) approach to accomplish this concern. Regardless, implicit SOAP headers in a contract require extra coding on the part of a consumer.
doesn't mention how the Documentum server can
consume WS-Security messages. For example, how do I configure Documentum Server to accept SAML 2.0 messages and integrate with other technologies such as Oracle OIF, PingIdentity or OpenSSO.
Not that I expect Craig Randall to provide a response, but I do hope that he will share more details on how things should work at a deeper level...
