Ability to remove LTPA expired tokens

Hi Amber,

We have previously requested more clarifying information. Because the additional information was not provided , this request has been closed.

Thank you for your interest in the Cúram SPM product.
Shane McFadden, Cúram SPM Product Management team

Hi Amber,

Just a reminder of the outstanding extra questions regarding this request which will help us fully evaluate your request.

Thank you,
Shane McFadden, Cúram SPM Product Management team

Hi Amber,

We are trying to understand what functionality is trying to access the server with expired LTPA token from the browser. We discussed was there anything like a heartbeat for the application OOTB but could not think of anything.

Have you customized anything OOTB to provide this or have you configured WebSphere to provide such a feature?
This is not something we have seen in our testing here so we need to try and understand what your application is doing with regards to trying to access the application with these expired LTPA tokens.

Thank you,
Shane McFadden, Cúram SPM Product Management team

Hi Amber,

We received the error logs fine and are analyzing them now.

Thank you for providing them and we will provide another response when our investigation is complete.

Thank you,
Shane McFadden, Cúram SPM Product Management team

I sent you the error logs but I got an email stating you still require more information on this enhancement request. Let me know because I had submitted the information you requested. Thank you

Hi Amber,

In order to evaluate your request, we require that you provide more detail so that we can fully understand this request.

We would like to see the error messages which you are referring to so that we can determine if they are SPM application error messages or WAS messages.
Could you provide an example of the logs you are referring to?

Thank you,
Shane McFadden, Cúram SPM Product Management team

I have provided additional information please let me know if there is anything further you require. Thank you.

I attached a document which includes the error logs. We are requesting an enhancement that would stop websphere from retrying the login to get a valid LTPA token repetitively.

Issue Description
We are having issues with WebSphere flooding our error log with LTPA errors. This has caused server performance issues. And recently, an overpayment case generation functionality seemed to be impacted as well.
This occurs when a user forgot to log out of the application and after the LTPA token eventually expired. The same error appears over and over again as WebSphere insists to keep retrying to get a valid LTPA token. The issue goes away if we call the user and ask her to log back into LINKIN again.
Here is an example of repetitive log stack trace entries, in SystemErr.log

There is an entry in SystemOut.log corresponding to this error. It just indicates our customized login module was invoked.
[11/22/19 9:45:08:220 CST] 00000182 SystemOut O ***** LINKIN LOGIN MODULE TRACE SETTING IS SIMPLE :: 2FA IS ENABLED *****
[11/22/19 9:45:08:220 CST] 00000182 SystemOut O ***** LINKIN LOGIN MODULE TRACE SETTING IS SIMPLE :: ****LINKIN Initialization complete *****

Attachment (Use case)

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Watson Health
Product family - Cúram Social Program Management
Product - Social Program Management Platform
Component - Functionality
Source - Other

For recording keeping, the previous attributes were:
Brand - Watson Health
Product family - Cúram Social Program Management
Product - Child Welfare
Component - Functionality
Source -

Hi Amber,

Thank you for your enhancement request.
We require some further analysis to determine whether or not this enhancement can be considered in a future release.
I will provide another response when our investigation is complete.

Thank you,
Shane McFadden, Cúram SPM Product Management team