Hi,
How do we know if a users has access to CWS ? We are looking to deploy a process which would use CWS to create Binders, Folders, etc. We want to make sure that the users that runs the proces has access to CWS.
Thanks.
Hi Tim,
There shouldn’t be any special perms necessary – it’s all beholden to the standard CS permissions model. i.e. if a user can create a folder in a particular location via the UI then the same user can do so programmatically through a web service application (or REST, etc.). If you don’t have permissions within content server it will throw a catchable exception.
AK
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Wednesday, October 18, 2017 3:21 PMTo: eLink Recipient <devnull@elinkkc.opentext.com>Subject: Access to Content Web Service
Access to Content Web Service
Posted by Saunders, Tim On 10/18/2017 03:13 PM
[To post a comment, use the normal reply function]
Forum:
Content Server Development Forum
Content Server:
Knowledge Center CS16
Thanks Alex. We had someone sign into the server with the service account and confirmed that he was able to log in and navigate to the desired folder and could create objects in the folder. However, when we try to use CWS we're receiving the following error:
2017-10-19 09:39:56,906 [1] INFO OpenTextWebService.Program [(null)] - Token Failed: Core.LoginFailed , ... Retrying
2017-10-19 09:39:57,015 [1] INFO OpenTextWebService.Program [(null)] - Token Failed: Core.LoginFailed , ... Retrying
2017-10-19 09:39:57,093 [1] INFO OpenTextWebService.Program [(null)] - Token
It's obviously not a passowrd issue so any idea why the user can authenticate through the UI but not via CWS?
Hmm… that seems pretty vague on the surface and I couldn’t tell you what your code is trying to do at that point. Where is that log coming from? Are you able to successfully get an auth token from the Authentication web service at all?
Token failed makes it sound like you’re passing in a stale or expired auth token on some call. Or perhaps you’re hitting a load balancer? The token from one instance won’t typically work on another so sticky sessions will be your friend – or simply connect direct to a dedicated front-end for web service access.
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Thursday, October 19, 2017 10:49 AMTo: eLink Recipient <devnull@elinkkc.opentext.com>Subject: RE Access to Content Web Service
RE Access to Content Web Service
Posted by Saunders, Tim On 10/19/2017 10:44 AM
Topic:
RE Access to Content Web Service Posted bySaunders, TimOn 10/19/2017 10:44 AM Thanks Alex. We had someone sign into the server with the service account and confirmed that he was able to log in and navigate to the desired folder and could create objects in the folder. However, when we try to use CWS we're receiving the following error: 2017-10-19 09:39:56,906 [1] INFO OpenTextWebService.Program [(null)] - Token Failed: Core.LoginFailed , ... Retrying2017-10-19 09:39:57,015 [1] INFO OpenTextWebService.Program [(null)] - Token Failed: Core.LoginFailed , ... Retrying2017-10-19 09:39:57,093 [1] INFO OpenTextWebService.Program [(null)] - Token It's obviously not a passowrd issue so any idea why the user can authenticate through the UI but not via CWS? Thanks.[To post a comment, use the normal reply function]Topic:Access to Content Web ServiceForum:Content Server Development ForumContent Server:Knowledge Center CS16
This is the code my developer is using:
try
{
authToken = authClient.AuthenticateUser(username, password);
tokenSuccess = false;
}
catch (FaultException e)
logger.Info($"Token Failed: {e.Code.Name} , {e.Message} ... Retrying");
And the returned error is: Token Failed: Core.LoginFailed , ... Retrying
This works using the developer's ID, it's just failing for the service account
To me that looks like if you make sure the service account and developer account is made identical in every fashion it should work
Any call to livelink will be checked first by OTDS if that is the method being used,I am not seeing that in your code which means that the
developer account is probably a "manual user" so if the service account can also be made a manual user in every respect like if the dev account has SA creds I would give the service account SA creds.
The simplest test I would do is as the service account user log on to the box that the CWS is configured.Install the free SOAPUI program.Source the WSDL's , then call the Authenticate User against that if it works you have proved it .If you are not a programmer yourself SOAPUI testing will take not more than 10 minutes.