getSessionExpirationDate exception in CWS 16.2.2

We recently upgraded to Content Server 16.2.2 and I decided to run a performance test driver I had used on CS 10.5 in my local environment.

While the code ran faster, the authentication token expired faster than it had in 10.5.

CS is configured to expire 30 minutes after the last request.
We are using internal OTDS on our local dev boxes.

KB Article KB4638995 mentions using GetSessionExpirationDate to keep track of when the session will expire.
The KB article shows a C# snippet where GetSessionExpirationDate appears to take an auth argument ( GetSessionExpirationDate(ref auth); ).
That is not an option with the Java implementation.

I had tried this before with 10.5 and it threw an exception. It still does in 16.2

Here is the code that I've been using:

// SESSION_EXPIRY_DATE is of type XMLGregorianCalendar
// AUTHENTICATION_TIME logic is for my own session handling routine

  // Call the AuthenticateUser() method to get an authentication token
  try
  {
   System.out.print("Authenticating User...");
   authToken = authClient.authenticateUser(USERNAME, PASSWORD);
   System.out.println("SUCCESS!\n");
   AUTHENTICATION_TIME = cal.getTime();
   cal.setTime(AUTHENTICATION_TIME);
   cal.add(Calendar.MINUTE, 30);
   AUTHENTICATION_TIME = cal.getTime();
   SESSION_EXPIRY_DATE = authClient.getSessionExpirationDate();
   System.out.println("Session expires at " + dateFormat.format(SESSION_EXPIRY_DATE));
  }
  catch (SOAPFaultException e)
  {
   System.out.println("FAILED!\n");
   System.out.println(e.getFault().getFaultCode() + " : " + e.getMessage());
   e.printStackTrace();
   return;
  }

Here is the result:

Starting test at 2017/10/11 11:21:19
Authenticating User...SUCCESS!

FAILED!

ns0:Core.LoginFailed : ?
javax.xml.ws.soap.SOAPFaultException: ?
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(Unknown Source)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at com.sun.proxy.$Proxy25.getSessionExpirationDate(Unknown Source)
at PerfTestCreatedoc.main(PerfTestCreatedoc.java:121)

I have also attempted using the refreshToken method with similar results.

Any feedback on what I am doing wrong, or where the issue may be?

Thanks...Brad

Find more posts tagged with

Comments

Appu Nair

I can get that command work like this

<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><HERE I PUT THE AUTHENTICATION TOKEN WHICH I GOT FROM AuthenticateUser></urn:AuthenticationToken>

</urn:OTAuthentication>

</soapenv:Header>

<soapenv:Body>

<urn1:GetSessionExpirationDate/>

</soapenv:Body>

</soapenv:Envelope>

If I do not put a authtoken I get your error

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Body>

<s:Fault>

<faultcode xmlns:a="urn:Core.service.livelink.opentext.com">a:Core.LoginFailed</faultcode>

</s:Fault>

</s:Body>

</s:Envelope>

There is also a RefreshToken both of them would expect to pass in a valid token.I don't know if it can be a date perhaps OT can

help

BTW I am probably not on your version I played with that on 16.2.0 (2017-03), build 41

Appu Nair
Principal Architect | Alitek
Website: alitek.com

From: eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com>
Sent: Wednesday, October 11, 2017 11:11 AM
To: eLink Recipient
Subject: getSessionExpirationDate exception in CWS 16.2.2

getSessionExpirationDate exception in CWS 16.2.2

Posted by Clarke, Brad On 10/11/2017 12:04 PM

We recently upgraded to Content Server 16.2.2 and I decided to run a performance test driver I had used on CS 10.5 in my local environment.While the code ran faster, the authentication token expired faster than it had in 10.5.CS is configured to expire 30 minutes after the last request.
We are using internal OTDS on our local dev boxes.KB Article KB4638995 mentions using GetSessionExpirationDate to keep track of when the session will expire.
The KB article shows a C# snippet where GetSessionExpirationDate appears to take an auth argument ( GetSessionExpirationDate(ref auth); ).
That is not an option with the Java implementation.I had tried this before with 10.5 and it threw an exception. It still does in 16.2Here is the code that I've been using: // SESSION_EXPIRY_DATE is of type XMLGregorianCalendar
// AUTHENTICATION_TIME logic is for my own session handling routine  // Call the AuthenticateUser() method to get an authentication token
  try
  {
   System.out.print("Authenticating User...");
   authToken = authClient.authenticateUser(USERNAME, PASSWORD);
   System.out.println("SUCCESS!\n");
   AUTHENTICATION_TIME = cal.getTime();
   cal.setTime(AUTHENTICATION_TIME);
   cal.add(Calendar.MINUTE, 30);
   AUTHENTICATION_TIME = cal.getTime();
   SESSION_EXPIRY_DATE = authClient.getSessionExpirationDate();
   System.out.println("Session expires at " + dateFormat.format(SESSION_EXPIRY_DATE));
  }
  catch (SOAPFaultException e)
  {
   System.out.println("FAILED!\n");
   System.out.println(e.getFault().getFaultCode() + " : " + e.getMessage());
   e.printStackTrace();
   return;
  }Here is the result:
Starting test at 2017/10/11 11:21:19
Authenticating User...SUCCESS!FAILED!ns0:Core.LoginFailed : ?
javax.xml.ws.soap.SOAPFaultException: ?
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(Unknown Source)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at com.sun.proxy.$Proxy25.getSessionExpirationDate(Unknown Source)
at PerfTestCreatedoc.main(PerfTestCreatedoc.java:121)I have also attempted using the refreshToken method with similar results.Any feedback on what I am doing wrong, or where the issue may be?Thanks...Brad

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	Knowledge Center CS16

Confidentiality Note: This message contains information, which may be privileged or confidential, or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee responsible for delivering the message to the intended recipient, you are hereby NOTIFIED that any dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you receive this message in error, please notify sender immediately.

Nizar Ghazal

I have a CS 16 system, and I'm able to do it with the following:

static void Main(string[] args)
{
// The user's credentials
string username = "Admin";
string password = "livelink";

// Create the Authentication service client
CS16Auth.AuthenticationClient authClient = new CS16Auth.AuthenticationClient();
CS16_OTDS.AuthenticationClient OTDSclient = new CS16_OTDS.AuthenticationClient();
CS16_OTDS.OTAuthentication OTDSotAuth = new CS16_OTDS.OTAuthentication();
CS16Auth.OTAuthentication cwsOTAuth = new CS16Auth.OTAuthentication();

// Store the authentication token
DateTime? Expiration = null;
string authToken = null;
string cwsToken = "";

// Call the AuthenticateUser() method to get an authentication token
try
{
Console.WriteLine("Authenticating User...");
Console.WriteLine("");
authToken = OTDSclient.Authenticate(ref OTDSotAuth, username, password);
Console.WriteLine("Success!" + " " + authToken);
Console.WriteLine("");
cwsToken = authClient.ValidateUser(authToken);
Console.WriteLine("Success!" + " " + cwsToken);
Console.WriteLine("");
cwsOTAuth.AuthenticationToken = cwsToken;
Expiration = authClient.GetSessionExpirationDate(ref cwsOTAuth);
Console.WriteLine("Expiration time = " + Expiration);
}
catch (Exception e)
{
Console.WriteLine("Failed!");
Console.WriteLine("{0} : {1}\n", e.Data, e.Message);
return;
}
finally
{
// Always close the client
Console.ReadKey();
authClient.Close();
}