No valid token set for this call

Hi,

We are currently working in Content WebServices integration using C# for Microsoft.NET 4.0. We have been receiving an error message after the authentication process. The error message is “Unable to authenticate: com.opentext.ecm.services.cap.InvalidTokenArgumentException: No valid token set for this call”

Our code is something similar to this:

Authentication.AuthenticationClient authClient = new Authentication.AuthenticationClient();
DocumentManagement.OTAuthentication dmAuth = new DocumentManagement.OTAuthentication();
DocumentManagement.DocumentManagementClient dm = new DocumentManagement.DocumentManagementClient();

string token = authClient.AuthenticateUser(userName, password); // OK. For example returns "Cde9vBVWEgA%2F0AuwGqzRQ3ncPODtxtrrV7vANhAmn4U%3D"
dmAuth.AuthenticationToken = token; // OK
DocumentManagement.Node folder = dm.GetNode(dmAuth, 90646); // ERROR

What could be the problem? Is a deploy or develop problem?

Thanks in advance

Marcelo

Find more posts tagged with

Comments

Ferdinand Prantl

If you deployed not only LL EWS but also RCS (alone or as a part of Enterprise Library) look at the second page of this thread: https://knowledge.opentext.com/go/17844967.

--- Ferda

severino_jose

I read the post you suggested me. I understood that I must implement authentication process using RCS authentication, not EWS authentication.

How must I do that? I have two authentication webservices:

- http://localhost:8080/les-services/services/Authentication
- http://localhost:8080/ot-auth/services/Authentication

In the first one there is a "AuthenticateUser" method that receives an "username" and "password" parameters, and returns a token. The second one has a "Authenticate" method that receive a "ref OTAuthentication" parameter, and "username", "password" and "domain"

Wich of them I must use? I tried with both, and the error message is the same.

Thanks

Ferdinand Prantl

Yes, you understood it right. This was my original code:

Authentication.Authentication authentication = new Authentication.Authentication();

string authenticationToken = authentication.AuthenticateUser("Admin", "...");

authentication.OTAuthentication authenticationValue = new Authentication.OTAuthentication();

authenticationValue.AuthenticationToken = authenticationToken;

authentication.OTAuthenticationValue = authenticationValue;

string authenticationToken2 = authentication.ImpersonateUser("myuser");

DocumentManagement.OTAuthentication authenticationValue2 = new DocumentManagement.OTAuthentication();
authenticationValue2.AuthenticationToken = authenticationToken2;
DocumentManagement.DocumentManagement documentManagement = new DocumentManagement.DocumentManagement();
documentManagement.OTAuthenticationValue = authenticationValue2;
...

I added another web reference to my project pointing to the CAP authenticating service in RCS and replaced the first block getting the authenticationToken2:

CapAuthentication.AuthenticationService authenticationService = new CapAuthentication.AuthenticationService();
string authenticationToken = authenticationService.Authenticate("Admin", "...", "");
CapAuthentication.OTAuthentication authenticationValue = new CapAuthentication.OTAuthentication();
authenticationValue.AuthenticationToken = authenticationToken;
authentication.OTAuthenticationValue = authenticationValue;
string authenticationToken2 = authenticationService.Impersonate("myuser", authenticationToken);

My real scenario was a service doing user impersonation so I used authenticationToken2 but if you have the credentials of the actual user the the first token string is enough.

I evaluated the first version of LES and ELIB WS two years ago. I did not test the most recent versions of both products.

--- Ferda

severino_jose

Thanks Ferdinand,

I tried the tips you suggested me. My CWS version seems to be more recent. I don't have the "AutenticationService" class in my RCS auth webreference (http://localhost:8080/ot-auth/services/Authentication), but there is an "AuthenticationClient" instead.

I read in previous posts that I must install the "LesAuthDriver" CAP Authentication Driver so that CAP can authenticate with Content Server. I followed these steps to install it:

- Opened "Open Text Administration" console
- Selected "Runtime and Core Services" and then "Authenticacion" and then "Drivers"
- In this place added "New driver" with this information
- Name: LesAuthDriver
- Type: LesAuthDriver
- les.host: localhost
- les.port: 8080
- les.admin.name: rcsadmin
- les.admin.password: rcsadmin
- Confirm les.admin.password: rcsadmin

The "rcsadmin" is the console user and pass.

In my server there is another configuration for the CAP server.

- Opened "Open Text Administration" console
- Selected "Runtime and Core Services" and then "Configuration" and then "CAP Server"
- There are these parameters:
- CAP Token Encryption Key: ce5xxxxxxxxx
- CAP Token Expiry Time: 24
- Database Table Prefix: cap_
- Legacy Domains: <empty>
- Remote CAP Port: 8765
- Trusted CAP Passphrase: *******

But I did not have any success autenticating via RCS

My code is this:

RCSAuthentication.AuthenticationClient authClient = new RCSAuthentication.AuthenticationClient();
RCSAuthentication.OTAuthentication otAuth = new RCSAuthentication.OTAuthentication();
        string token;
        string userName = "rcsadmin";
        string password = "rcsadmin";
token = authClient2.Authenticate(ref otAuth, userName, password, "");

This last line fails now with the same error. I don't know what I must pass for the otAuth param. There is only one "Authenticate" method with the showed parameters

I think this is a driver installation problem.

Any help? How must I test the driver installation?

Thanks in advance

Appu_Nair

I think you are doing the LESAuthDriver incorrectly.Unless you have livelink running in tomcat server which you should confirm with the livelink people there usually this is how livelink runs in many companies

Livelink runs on IIS mostly port 80

Livelink's app server port is 2099

If what i am saying is true then the LESAuthDriver is configured as

then your entries will be like

les.admin.name =Admin #any SA privileged user in Livelink will do

les.admin.password=the password of that user

Host livelik server host

port =2099 (you should ask the admin there where it is litening for lapi requests)

this is the setting we allow for SAP to call RCS into livelink for Enterprise lib Svcs from the SAP side.I nevr have messed with the cap driver

Jason_Smith

Hi Jose,

To test the driver installation you can try logging into the Admininstration client as the Content Server Admin user you set up the driver with. If the driver is set up properly you should be able to login and view the contents of the Content Server node in the Administration client.

At a quick glance it looks like you set up the driver with the wrong values. The username/password should be the Admin user's credentials for Content Server. The port is the Content Server port, so the default is 2099.

Hope this helps.

Jason

severino_jose

Sorry, I have CWS running over tomcat server.

This is the webservice definition for the cap server.

Endpoint

Information

Service Name:	{urn:auth.services.ecm.opentext.com}AuthenticationService
Port Name:	{urn:auth.services.ecm.opentext.com}AuthenticationPort

Address:	http://localhost:8080/ot-auth/services/Authentication
WSDL:	http://localhost:8080/ot-auth/services/Authentication?wsdl
Implementation class:	com.opentext.ecm.api.cap.ws.impl.CapWebService

The main method is

string Authenticate (ref OTAuthentication otAuth, string username, string password, string domain)

What must I pass to the otAuth param? I have been passing an empty OTAuthentication class, but always fail.

Ferdinand Prantl

Looking at the example at https://knowledge.opentext.com/go/15423140, they authentificate firstly their application, then their effective user:

const string APPL_NAME = "ClientExample";
const string APPL_PSWD = "livelink";
const string USER_NAME = "Admin";
const string USER_PSWD = "livelink";
const string USER_DOMN = null;

AuthService.OTAuthentication _otAuth = null;
string tokenA = authService.AuthenticateApplication(ref _otAuth, APPL_NAME, APPL_PSWD);
string tokenU = authService.Authenticate(ref _otAuth, USER_NAME, USER_PSWD, USER_DOMN);

_otAuth appears to be filled by the first call.

I didn't test this myself - ELIB 1.0 had different WS API - but the web site on OTDN with documentation and examples about ELIB should help (https://knowledge.opentext.com/knowledge/llisapi.dll/open/15106296).

--- Ferda

severino_jose

Ferdinand, thanks very much for all your help

I tried the sample code you suggested me.

string tokenA = authService.AuthenticateApplication ( ref _otAuth, "ClientExample", "livelink" );

After this line I received a new error message: "not for this domain LesAuthDriver"

My params are the same in the sample. My LesAuthDriver in the server has an empty domain.

What's the meaning of this error?

Ferdinand Prantl

I'm afraid that I don't know. I haven't seen it and haven't worked with more recent version of ELIB. If fixing the configuration suggested by the others here doesn't help I'd suggest asking for help in the ELIB forum I pointed to. RCS are used usually with ELIB and not with standalone LES. You could also open a support case with OT yourself or on behalf of a paying customer.

Just out of curionsity - you seem to need just the functionality of LES WS - why did you deploy the ELIB/RCS WS too?

--- Ferda

severino_jose

Ferdinand,

It worked !!!

The solution for the problem has two aspects:

1.- LesAuthDriver
    - Name: LesAuthDriverCLB
    - Type: LesAuthDriver
    - les.host: localhost
    - les.port: 2099
    - les.admin.name: admin
    - les.admin.password: livelink

2.- Code fixes. Setting otAuth to NULL previous to call Authenticate.

RCSAuthentication.AuthenticationClient authClient = new RCSAuthentication.AuthenticationClient();
RCSAuthentication.OTAuthentication otAuth = new RCSAuthentication.OTAuthentication();
DocumentManagement.OTAuthentication dmAuth = new DocumentManagement.OTAuthentication();
DocumentManagement.DocumentManagementClient dm = new DocumentManagement.DocumentManagementClient();

otAuth = null; // This line makes the difference
token = authClient.Authenticate(ref otAuth, userName, password, null);
dmAuth.AuthenticationToken = token;
DocumentManagement.Node folder = dm.GetNode(dmAuth, 90646);

There was not necessary application authentication.

Thanks a lot for your all your help.