Upload a file with a different user to CS using CWS

Shai Abadi · 2021-10-27T08:44:06+00:00

There was an error rendering this rich post.

Greetings,

I was wondering if there is an option to upload a file and set a different user as the uploader. Not the one that I was authenticated with (CWS).

The regular scenario is that I create a token that was authenticated with Admin as a user and then with the token's ref I upload content with CreateDocument() and UploadDocument() methods.

I was wondering if there is an option to use additional user instead. Admin user will use the CWS's and I'll choose a different user to upload a file.

Thanks.

Find more posts tagged with

Comments

MangeshThorat

Hi Shai Abadi

Even i am looking to achieve same but using REST API. Please let me also know if you found any way.

Regards,

Mangesh Thorat

Appu Nair

That is what the ImpersonateUser calls are for. In old livelink CWS or SOAP interfaces, the Authentication service has a impersonate user method.

The ground rules for impersonation are

You have to first authenticate to Livelink as a user with a System administration profile. the user 'Admin' or the root user of livelink is a special SA. Any SA can do it.
With the token, you get from one you ask the token to be that of X user.
With the advent of the OTDS pass-through API which is kind of the one-stop-shop for all Authentication(including complicated scenarios like dual-factor). The OTDS restapi has a simpler one that takes the two users and gives you an impersonated token, in soap, I think you have to do the double-take.
The reason why you have to get a first superuser token to impersonate another is so that the audit activities can indicate that a SU context was used prior, but it would look no different than the actual interactive user did.

https://knowledge.opentext.com/knowledge/cs.dll/Open/67792619

I found a namespace core but usually, the methods you want are part of the Authentication wsdl.

In the old CWS forum there are at least a dozen examples of this based on Java clients and C#

Appu Nair

@MangeshThorat as I replied earlier it is much easy to do this REST

The logic I employ in a product I wrote is OTDSSERVER/otdsws/rest/authentication/credentials here you give the System Admin User who is known in OTDS and the resource.

I retrieve it and I then execute /authentication/ticketforuser

As I said there is a single call to do all this if you look at swagger you will see it.

MangeshThorat

Thank you sooo much @Appu Nair 😀

I just came across with below article which i found very useful for implemeting Impersonate User using REST API.

https://knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/KB8295770

It helped me alot. Hope it helps everyone. Hence sharing... 😄

Cheers!✌️

Appu Nair

@MangeshThorat the difference between the way I do and the OT article is the article shows the auth endpoint of the CS REST API. I have noticed that when you go via the OTDS and get an OTDSSSO* ticket this will be preferred by all CS Resources and won't get rejected based on individual CS settings(the mostly the bad way that the LB is set up). My product is a B2B interface, not a typical mobile application hence I chose that way.

Nevertheless, the above link will most certainly work.

MV Adam

I'll add my recent experience:

OTDS used to have a GetTicketForUser SOAP method but that was deprecated sometime prior to our current version, 20.4 (it worked in 16.2.8).

You'd first authenticate using an admin level login, and then call that method.

In 20.4, I had to use the OTDS rest authentication/ticketforuser operation. That returns a ticket that you can pass into the CS Authentication service, ValidateUser method (OpenText confirmed this)