"Authorization failed" DFS error - help!

I posted a message a day ago regarding not being able to get the HelloDFS .NET sample application to run. I was running the sdk on a Windows 2003 box without modifying the sample code (other then setting the address, repository, username and password) and utilizing the .NET productivity layer. I'm using the default DFS installed on the Content Server box, which is SUSE Linux 10 box. When I run the sample, I get the following error:

{"Authorization failed, please review identities provided in service context \"temporary /127.0.0.1-1233674717250-839111712\""}

Shouldn't the IP address at the end of the error message be that of the Content Server and not local host? The one thing I did not do was modify the dfc.properties docbroker IP Address ... could this be causing the error? Doesn't the address parameter passed through the code over-ride the dfc.properties settings? I can't test this out today, so any feedback would be appreciated.

Find more posts tagged with

Comments

Oleg

Please check the root cause of your exception, it should point you in the right direction.

Yes, you have to change dfc.properties to point to your docbroker.

csebourn

Hi,

Does your stack trace include the following error message:

Caused by: java.lang.NoClassDefFoundError

at sun.reflect.NativeConstructor.AccessorImpl.newInstance0(Native Method)

If so, this problem is due to some missing DFC jars in your ear file (bug DFS-733).

To correct this, in your build.xml file, change the <packageservice><pathelement> for DFC by changing the DFC.jar to *.jar to include all jars in this directory as follows:

Re-package and re-deploy your ear file.

Please let me know if this solves your problem.

Thanks

wendi7

I am having the same problem with a client I created that is calling a DFS service. It is a .NET app so doesn't have a build.xml. Any other possible solutions? Here is my full error stack is there a reason that the error below is pointing to location 127.0.0.1 when I have my App.config pointing to the correct services server?):

Emc.Documentum.FS.Runtime.ServiceInvocationException was unhandled
Message="Service method \"Create\" invocation failed."
Source="Emc.Documentum.FS.Runtime"
StackTrace:
       at Emc.Documentum.FS.Runtime.Context.Impl.ClientReflectionServiceInvoker.Invoke(Object proxy, MethodInfo method, Object[] args)
       at Emc.Documentum.FS.Runtime.Context.Impl.SoapClientInvocationHandler.Invoke(Object proxy, MethodInfo method, Object[] arguments)
       at Emc.Documentum.FS.Runtime.Context.Impl.UcfClientInvocationHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
       at Emc.Documentum.FS.Runtime.Context.Impl.HttpSessionInvocationHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
       at Emc.Documentum.FS.Runtime.Context.Impl.ContextThreadLocalInvocationHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
       at Emc.Documentum.FS.Runtime.Context.Impl.ReturnedContentTransformationHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
       at Emc.Documentum.FS.Runtime.Context.Impl.ServiceContextInvocationHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
       at $Proxy0.Emc.Documentum.FS.Services.Core.IObjectService.Create(DataPackage , OperationOptions )
       at Gis2Dctm.DFSClient.createDocumentWithContent(String repository, IObjectService objectService, String filePath, String folderPath, String airport, String location, String level) in C:\Users\taylorwil\Documents\Visual Studio 2008\Projects\Gis2Dctm\Gis2Dctm\DFSClient.cs:line 200
       at Gis2Dctm.DFSClient.startLogic(String repository, String userName, String password, String projectNo) in C:\Users\taylorwil\Documents\Visual Studio 2008\Projects\Gis2Dctm\Gis2Dctm\DFSClient.cs:line 89
       at ConsoleApplication1.Program.Main(String[] args) in C:\Users\taylorwil\Documents\Visual Studio 2008\Projects\Gis2Dctm\ConsoleApplication1\Program.cs:line 12
       at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
InnerException: System.ServiceModel.FaultException
       Message="Authorization failed, please review identities provided in service context \"temporary/127.0.0.1-1248344355563-1812431982\""
       Source="mscorlib"
       StackTrace:
         Server stack trace:
            at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
            at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
            at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
            at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
         Exception rethrown at [0]:
            at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
            at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
            at Emc.Documentum.FS.Services.Core.ObjectServicePort.create(createRequest request)
            at Emc.Documentum.FS.Services.Core.ObjectServicePortClient.Emc.Documentum.FS.Services.Core.ObjectServicePort.create(createRequest request)
            at Emc.Documentum.FS.Services.Core.ObjectServicePortClient.Create(DataPackage dataPackage, OperationOptions options)
       InnerException:

r.wetzlmayr

I received this error messsage while I tried to run the inital HelloDFS .NET sample from the Documentum Foundation Services (DFS) Getting Started quick start guide in a Documentum 6.5 SP1 environment on Windows.

I verified username, docbase name and password and even tried to both include and omit the Windows domain name as the fourth parameter to the RepositoryIdentity constructor - without any success.

The "Verify repository login information" chapter in the Getting Started with Documentum Foundation Services.pdf document lists "user name of a user with Create Cabinets privilege" as a prerequisite for authentication. I have not found the user's capability to create cabinets to make any difference for this issue. It did neither work for users with or without "Create Cabinet" permissions.

In my case, the reason for this error was the Documentum Java Method Server using an outdated docbroker which made all attempts to authenticate any valid user fail.

The Documentum Java Method Server's log file provided the first useful hints on how to triage this problem.

According to the Documentum Foundation Services Deployment Guide, you may find this log file at <DRIVE:>\Documentum\jboss4.2.0\server\DctmSErver_MethodServer\log\server.log if the Java method server was deployed as a part of the Content Server installation. Numerous entries stating "[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "docbroker$foo:1489" failed" hinted to a stale hostname which no longer existed on our network.

<DRIVE:>\Documentum\jboss4.2.0\server\DctmServer_MethodServer\deploy\dfs.ear\APP-INF\classes\dfc.properties included <DRIVE:>\Documentum\dfc.properties, which held no traces of the stale docbroker name at all.

Obviously, the Documentum Java Method Server was using outdated information so restarting the service caused the correct entries from <DRIVE:>\Documentum\dfc.properties to be reread and thus resolved this issue.

StevenE

I have recently had this issue and this is the way I managed to solve it:

When you are in Composer, with your Documentum Web Service project open, change to the Web perspective. This will allow you to see the referenced DocumentumCoreProject.
Navigate down the DocumentumCoreProject as follows: /DocumentumCoreProject/dfs6.5/emc-dfs-sdk-6.5/etc and open the dfc.properties file.
Edit this file with the information pertinent to your environment:

dfc.docbroker.host[0]=my_server
dfc.docbroker.port[0]=1489
dfc.globalregistry.repository=documentum
dfc.globalregistry.username=dm_bof_registry
dfc.globalregistry.password=KmYwfPemffMsdfrfprSphRf5Lwazsdfxg\=\=
Save the dfc.properties file.
Validate and Build your Project
Export to an EAR file using the Composer Export Service Archive tool - i.e. right-click your custom Documentum Web Service project and select Export, then choose Documentum/Export Service Archive.

Hope this helps.