Connection to DocumentManagement WebService through SoapUI

Hello,

in a precedent Topic, i have read the possibility to call DocumentManagement Web Service through standard webservice client (like SoapUI, XMLSpy, etc..) using AuthenticationToken returned by the call to the Authentication Service's AuthenticateUser method.

My problem doing this procedure, is the "Invalid Username/Password" response.

Below the step I execute:

1) Get Authentication Token through Java Code;

2) Call one Web Service Operation through SoapUI with token returned on Soap Header;

Is this procedure correct or isn't possible doing this? If is correct, why i'm getting Login Error?

Thank you very much.

Find more posts tagged with

Comments

sgrasley

Hi, Gianlorenzo.

I just ran a quick test using soapUI and it worked fine. I tried using Java and soapUI itself for retrieving the authentication token and both worked.

Perhaps using soapUI to retrieve the authentication token will work better in your situation?

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

Thanks Scott,

how can I use SoapUI to get Authentication Token? I don't see any Operation for doing this...

Are there some configurations in OpenText for accepting external connections?

In SoapUI is necessary to use also HTTP Authentication?

sgrasley

Hi, Gianlorenzo.

Please see Authenticating the Client in the Client Guide.

HTTP Authentication is not required by the web services. That said, an OTAuthentication SOAP Header is required, and should be part of the template request that soapUI generates. The token used in this header should come from the Authentication service's AuthenticateUser method.

Thanks,

Scott

sgrasley

Sorry, Gianlorenzo, I didn't address your "external connections" question. Could you elaborate on what you're asking, please?

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

Hi Scott,

thank for your patience. I'm trying to do a simple GetNode Method call on SoapUI insert into Soap Header Authentication Token get by AuthenticationUser method's (through SoapUI call). Unfortunately response i get from SoapUI is LoginFailed: Invalid Username/Password.

Where am i doing wrong? it seems token is no longer valid.

Gioanlorenzo_Magnani_Mejo

Hi Scott,

doing some tests about this scenario, we discovered that calls through SoapUI work with Web Service deployed on IIS Application Server while don't work if are deployed on Tomcat. Maype we did something wrong in Web Service deployment on tomcat? Is there any configuration to do on Tomcat?

In Java Web Service Installation guide says: "Modify the livelinkServer, LivelinkServerPort and LivelinkEncoding context parameters as appropriate for your Livelink installation". Maybe this parameter (like LivelinkEncoding) are uncorrect?

Thanks a lot.

sgrasley

Hi, Gianlorenzo.

I don't think a mismatch in encoding would cause the login failed message. What is the encoding value set to?

Are both requests from soapUI using the same application server? If one is against IIS and the other Tomcat, then that could be problematic.

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

Hi Scott,

encoding actually is set to UTF-8. I noticed that the token contains Special Chars: if encoding is wrong calls maybe return Invalid Username/Password because this special chars are replaced with wrong string.

Could be this the problem? If yes, is sufficient change to ISO-8859-1 ?

Thanks

sgrasley

Hi, Gianlorenzo.

There shouldn't be any special characters in the authentication token...

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

In Token we get from Authentication Service's, there is Percent Character (%).

sgrasley

Oh, OK. % should be handled fine between UTF-8 and Latin1, so no problem there. There must be something else going on. Can you post the requests and responses?

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

This is Soap Message for Simple GetNode's Request.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:DocMan.service.livelink.opentext.com">

<soapenv:Header>
      <urn:OTAuthentication>
         
         <urn:AuthenticationToken>RZgKnFxsaxXtV2xJ035X%2BiKUgtUy3Qt9RXWZKsmEUWg%3D</urn:AuthenticationToken>
      </urn:OTAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <urn1:GetNode>
         <urn1:ID>2003</urn1:ID>
      </urn1:GetNode>
   </soapenv:Body>
</soapenv:Envelope>

The Reponse is simply Invalid UserName/Password.

sgrasley

Hi, Gianlorenzo.

I think I understand what is happening now. Try your request like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn1="urn:DocMan.service.livelink.opentext.com">
   <soapenv:Header>
      <OTAuthentication xmlns="urn:api.ecm.opentext.com">
         
          <AuthenticationToken>RZgKnFxsaxXtV2xJ035X%2BiKUgtUy3Qt9RXWZKsmEUWg%3D</AuthenticationToken>
      </OTAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <urn1:GetNode>
         <urn1:ID>2003</urn1:ID>
      </urn1:GetNode>
   </soapenv:Body>
</soapenv:Envelope>

If you deploy the les-services.war file contained in the cumulative patch for Content Server (after July 2009), I think you'll find that your original request will work.

Thanks,

Scott

cluttrell@alitek.com

I'm getting the same behavior from the Enterprise Library Version of Enterprise Web Services. Is there a patch available for that?

sgrasley

Hi, Chris.

Are you using EWS deployed under RCS (as part of an Enterprise Library deployment)? If so, I think you're experiencing a different problem.

Are you using the RCS authentication service (ot-auth) to obtain a token (instead of the EWS one)? Because RCS handles the authentication tokens in that scenario, its authentication service must provide one.

Thanks,

Scott

Ferdinand Prantl

I experienced this too. After deploying RCS (with ELIB Services) my application using LL EWS was broken because the authentication did not work anymore.

I would expect the LL EWS working regardless the RCS deployment or CS being delivered always with RCS. The public API should always work and be consistent and not break after the customer installs another module on the server. I consider this a bug in the design of the RCS integration. Not having a single consistent WS API is the main reason why we stay with LAPI for both LL971 and CS10 now. I hope that this will be fixed in the next CS release

--- Ferda

cluttrell@alitek.com

Yes. I am using the EWS deployed under RCS. The behavior is the same as described in this thread.

No. I am not using the RCS authentication (ot-auth). I'm using the Authentication web service within EWS.

Chris

sgrasley

Hi, Chris.

I think if you use ot-auth then all will be well.

Thanks,

Scott

cluttrell@alitek.com

I got my token back from ot-auth, but now when I perform a GetNode, I get the following error.

<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:Server</faultcode><faultstring>com.sun.xml.bind.v2.runtime.JAXBContextImpl</faultstring></S:Fault></S:Body></S:Envelope>

EWS doesn't seem to like the token from ot-auth. Any ideas? What about the bug that Ferdinand mentioned?

Chris

sgrasley

Hi, Chris.

That error message suggests that RCS doesn't like the token for some reason. Can you provide the request that you sent?

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

Hi Scott,

after we change Environment, we have problem to call any Service's using Token returned from AuthenticateUser method's. Error returned is:

com.opentext.ecm.services.cap.InvalidTokenArgumentException: No valid token set for this call.

This is one of the call we are trying:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:Core.service.livelink.opentext.com">
   <soapenv:Header>
      <urn:OTAuthentication>
         
<urn:AuthenticationToken>VaMQp%2B8x4CDyAsf7CMZ5rcGLKlrhi8FGKUPaqx0TfK8%3D</urn:AuthenticationToken>
      </urn:OTAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <urn1:ImpersonateUser>
         
         <urn1:userName>Admin</urn1:userName>
      </urn1:ImpersonateUser>
   </soapenv:Body>
</soapenv:Envelope>

Can you suggest us any configuration to do on Application Server? I remember to you that in precedent environment we didn't encountered to this kind of error.

Could be a Cookie Configuration Problem?

Thanks a lot.

sgrasley

Hi, Gianlorenzo.

If you have CWS deployed under RCS, then you have to use RCS' authentication service to obtain tokens.

In that case you'll want to add the LesAuthDriver CAP Authentication Driver so that CAP can authenticate with Content Server.

To impersonate users, use the RCS authentication service's DoSSO method.

Can you elaborate on what you are trying to do and what has changed in your environment?

Thanks,

Scott

Gioanlorenzo_Magnani_Mejo

Quoted Scott Grasley (sgrasley) on 2010/10/20 17:05:

Can you elaborate on what you are trying to do and what has changed in your environment?

Hi Scott,

it seems there isn't any changes from previous environment.

This error compair calling any other Services (GetNote, CreateFolder, CreateNode, etc..) so we are not be able to execute the request correctly.

Please can you explain how to add the LesAuthDriver CAP Authentication Driver?

Thank you very much.

sgrasley

Hi, Gianlorenzo.

I think your best option at this point is to open a support ticket. They might be better able to assist you.

I will say that CAP authentication drivers are configured through the Open Text Administration client. Just use that client to connect to the RCS server and use the UI to add an instance of LesAuthDriver for your Content Server, if one is not already there.

Thanks,

Scott

severino_jose

Hi,

I'm experiencing the same problem. After the authentication, the token seems to be invalid, showing the same error "Unable to authenticate: com.opentext.ecm.services.cap.InvalidTokenArgumentException: No valid token set for this call"

Did you find a solution for this problem? Do you think this is a deploy or develop problem?

Thanks in advance

Marcelo

Forest_Wang

Hi all,

I have the same problem. The error message is:

NOT AN IECMException:com.opentext.ecm.services.cap.InvalidTokenArgumentException: No valid token set for this call.

Does anybody know how to fix it? Thanks a lot advance.

Regards,

Forest.

Ferdinand Prantl

The error message appears the same as the one reported at https://knowledge.opentext.com/go/18652620. You may be able to get rid of it if the cause is the same in your environment.

--- Ferda