nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DFS authentication problem

terok

Hi,

my application uses DFS and last time (3 days ago) run went ok. No problems. Now when I'm trying to add a document to repository, I get an error "Caused by: com.emc.documentum.fs.rt.AuthenticationException: Authorization failed, please review identities provided in service context "temporary/127.0.0.1-1236682572557-6266533183904054873"

I start session like:

ContextFactory contextFactory = ContextFactory.getInstance();
serviceContext = contextFactory.newContext();

        RepositoryIdentity repoId = new RepositoryIdentity();
        repoId.setRepositoryName(repositoryName);
        repoId.setUserName(userName);
        repoId.setPassword(password);
        serviceContext.addIdentity(repoId);

        ContentTransferProfile transferProfile = new ContentTransferProfile();
        transferProfile.setTransferMode(ContentTransferMode.BASE64);
        transferProfile.setGeolocation("FI");
        serviceContext.setProfile(transferProfile);

(Note: I tried also to set empty identity arry to serviceContext at first and after that set new identity, and I tried too to getContext() instead of creating new one. No affects to error below)

Any ideas why this happens and how I can fix the situation? Where and how I can check temporary/ip-32432432432 thing ?

BR, Tero

Find more posts tagged with

Comments

techi_mad

hi terok,

by seeing the error i could understand that ur invoking service by getRemoteService. i had the same issue when firewall enabled.please look for ur firewall status. and check wether the user has the rights to create or import documents.

Regards,

Gangai.

rng5000

This situation can be soelve two ways using getRemoteService or adding the WSSE security header with your token to the DFS Request Header.

craigrandall

Let's be a bit more clear, shall we. There are two ways to solve this problem:

(1) If you are a direct-to-WSDL consumer, you need to ensure that you pass a ServiceContext header in your SOAP request message.

(a) See http://craigrandall.net/archives/2008/07/dfs-object-service-consumer-2a/, which establishes the problem context, and then

(b) See http://craigrandall.net/archives/2008/07/dfs-object-service-consumer-2b/, which solves the subject issue.

(2) If you are a productivity layer-based consumer, you need to register your ServiceContext instance.

(a) See http://craigrandall.net/archives/2008/07/dfs-object-service-consumer-1/, which demonstrates where registration occurs.

Cheers,

-Craig

baixench

Hi Craig,

I have readed your link about register a context with the productivity layer and I have one question:

After I have registred my context in my red class showing below, how can I reload it in another call?

This is my structure classes:

I have an encapsulated web service class --> web service --> class with client facilities .dll references added.

Thank you.

Cheers

terok

Hi,

thanks for the answers.I couldn't test them because problem disappeared after full server restart and has not been occured since.

So the cause of the problem is unknown and solution (restart can not be solution in any case..)

BR, Tero

baixench

Hi terok,

Be carefull with your problem, because it will reproduce again.

I think your problem is relationated wit session limit user (default 100 sessions per user).

Check in DA -- Andministration -- User Administration -- Sessions if it increases when you throw new requests.

Best regards

Zeleres

Craig,

Thank you for the detailed blog posts!!

I am also interested in finding how to use a registered service context after it has been registered. So far I have the following:

DMLib.cs -- Just a wrapper around some of the productivity layer calls (similar to dfs.cs)

ASPX page -- Instantiates the DMLib class and makes calls through that

In the ASPX page I have a method that sets up a new service context object. The ServiceContext object is registered and then stored in the ViewState (it's my understanding we are to store this on the client).

        public IServiceContext DMServiceContext
        {
            get
            {
                if (ViewState["DMServiceContext"] == null)
                {
                    ViewState["DMServiceContext"] = initializeContexts();
                }
                return (IServiceContext) ViewState["DMServiceContext"];
            }
            set
            {
                ViewState["DMServiceContext"] = value;
            }
        }

I then pass the ServiceContext object to the DMLib class when I instantiate it (just passed in the constructor).

  dmLibObject = new DMLib(DMServiceContext);

In that constructor I am just setting the private ServiceContext that is used in that class to the one passed in, but I get the following error when I attempt to call any methods from the DMLib.cs class:

Authorization failed, please review identities provided in service context

I believe this may be because I am not setting the private username, password, and repository strings inside the DMLib class. I had a similar problem to this before, and it was solved by setting those variables (see below):

        public extDMLib(string defaultRepository, string userName, string password)
        {
            repository = defaultRepository;
            this.userName = userName;
            this.password = password;

            Login();
        }

The problem is that, with a ServiceContext object, I do not have the username, password, or repository to set in the DMLib.cs class... Is there a way I can ge these, or is there a different method I should be using?

Thank you,

- Zach

bobbyw

I have read all of these questions and comments but still have a question. I am using the DFS productivity layer, and I have registered my servicve context successfully. I even figured out how to get my hands on the token using java reflection. My question is: Now What??

My application has multiple users. What I want to do is have the application log in as a super user and register the context and get all the service handles. Subsequently, I want each user to use their own userid and the token to invoke the services, without having to re-register a context, etc. etc., so that Documentum can record each user.

How does one make use of the token in the productivity layer?? Since one must pass in the context in the getRemoteService call, does each user have to modify the service context identity and issue his own getRemoteService call? Does each user have to register his own context?

I would appreciate some help, but please do not tell me what to do if I am NOT using the productivity layer, because I AM.

Thanks

Bobbyw

Zeleres

I've long since given up on using or caring about tokens using the .NET Productivity Layer. There was a time when I thought the tokens would be useful, but those days are gone. Now I'm just passing around the entire ServiceContext object and I've also learned that the ServiceContext object cannot be stored in the ViewState because it's not serializable, so it's now stored in the Session...

I'd be really interested if you find a way to use those tokens in the .NET Productivity Layer, but frankly I just totally gave up on the idea and moved on........

joel1607

Hi!

I have the same problem, I tried all that you described in the answers but nothing work, Anybady have anpther solution?. I'm working with java and productivity layer.

This is the trace:

com.emc.documentum.fs.rt.AuthenticationException: Authorization failed, please review identities provided in service context "temporary/127.0.0.1-1265830467375--1811100669470968044"
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.getExceptionInstance(ClientReflectionServiceInvokerCompat60.java:176)
        at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.invoke(ClientReflectionServiceInvokerCompat60.java:78)
        at com.emc.documentum.fs.rt.context.impl.SoapClientInvocationHandler.invoke(SoapClientInvocationHandler.java:66)
        at com.emc.documentum.fs.rt.context.impl.UcfClientInvocationHandler.invoke(UcfClientInvocationHandler.java:47)
        at com.emc.documentum.fs.rt.context.impl.MtomCompatHandler60SP1.invoke(MtomCompatHandler60SP1.java:55)
        at com.emc.documentum.fs.rt.context.impl.HttpSessionInvocationHandler.invoke(HttpSessionInvocationHandler.java:65)
        at com.emc.documentum.fs.rt.context.impl.ReturnedContentTransformationHandler.invoke(ReturnedContentTransformationHandler.java:45)
        at com.emc.documentum.fs.rt.context.impl.OperationOptionsHandler.invoke(OperationOptionsHandler.java:59)
        at com.emc.documentum.fs.rt.context.impl.ContextThreadLocalInvocationHandler.invoke(ContextThreadLocalInvocationHandler.java:51)
        at com.emc.documentum.fs.rt.context.impl.ServiceContextInvocationHandler.invoke(ServiceContextInvocationHandler.java:30)
        at $Proxy16.execute(Unknown Source)
        at control.Documentum.DocumentumServices.getDocumentFormat(DocumentumServices.java:864)
        at control.Documentum.DocumentumServices.main(DocumentumServices.java:108)
Caused by: DfServiceException:: THREAD: main; MSG: Failed to authenticate client. Please check server log for more detail.; ERRORCODE: ff; NEXT: null
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.getExceptionInstance(ClientReflectionServiceInvokerCompat60.java:144)
        at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.invoke(ClientReflectionServiceInvokerCompat60.java:77)
        ... 11 more

The problem starts when the server's IP changed

Please help me

zhou_simonq

For how to register service context, pls refer to Craig's articles listed above.

According to my experience, "Authorization failed" can be caused by different reasons. Actually, this error message is rather superficial and it may be caused by Content Server and DFC. So, we need to treat them one by one.

As I remember, there is bug in DFS .NET productivity layer and has been fixed in 6.5 SP2 and later versions. Also, there is a HFX available for 6.5 SP1.

This issue may also be caused by the configurations of Content Server and DFC, namely the session settings in server.ini and dfc.properties.

- simon