BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  Session Validation for CSHS

    Posted 05/23/20 06:22 PM
    Edited by Harish Gupta 05/24/20 02:53 PM
    Hi All,

    In my application, we have our BPM Dashboard located on an external application.We have implemented TAI so that once the user is authenticated by the external app the user can seamlessly login to the BPM Dashboard without re-login.

    we observed 2 issues.

    1. When we logout from the external app, the BPM Dashboard session still continues. Can we invalidate the BPM session when the user logout from the external portal?

    2. We have set the LTPA timeout to 120 mins but The CSHS does not time out even after 120 min. It eventually times out but only after 5-6 hours of inactivity. As far as I know, LTPA timeout does not need inactivity, even though user is actively working on the screen, the LTPA is supposed to expire after 120 mins.

    Thanks

    ------------------------------
    Harish Gupta
    ------------------------------


  • 2.  RE: Session Validation for CSHS

    Posted 05/25/20 02:00 AM
    Hi Harish,

    the "logged in" state in WebSphere (and thus BPM) is tracked using the LTPA cookie. Logout generally means to tell the browser "forget the cookie". Because of the same origin policy enforced by browsers, only the origin (as in https://bpm.customer.com) that has set the cookie can remove it.
    To logout from BPM at the time when you log out from some other app, you would need to redirect the user's browser to e.g. https://bpm.customer.com/ProcessPortal/ibm_security_logout

    Alternatively, your TAI can be configured to be invoked not only for unauthenticated requests, but for all requests. You'd need to update the TAI logic to 
    - check is an LTPA cookie is present
    - if so, determine the user id and call out to the other app and check logged in state there
    That's really expensive.
    Many variants are possible depending on the exact requirements (today and anticipated future requirements).

    Regarding CSHS timeout ...
    I am not sure what is supposed to expire here. LTPA might expire after 120, but your TAI might seamlessly reauthenticate the request for completing the CSHS. There shouldn't be server-side state, because CSHS were invented to scale to many browser clients without permanently occupying server side resources.

    ------------------------------
    Jens Engelke
    ------------------------------



  • 3.  RE: Session Validation for CSHS

    Posted 05/25/20 06:32 AM
    @Jens Engelke So what I get is, even though LTPA expires, the TAI will reset its expiry on reload of page?

    I observed that when I delete the browser cookies, I can successfully end the CSHS session. Can I do it programmatically?
    I tried to do it from JavaScript but it does not give me access to the HttpOnly LTPA cookies.

    ​

    ------------------------------
    Harish Gupta
    ------------------------------

    Original Message


  • 4.  RE: Session Validation for CSHS

    Posted 05/25/20 06:56 AM
    Edited by Jens Engelke 05/25/20 07:10 AM
    LTPA expiration cannot be reset. However, a TAI is invoked for unauthenticated requests (which includes requests with expired authentication) for protected resources. That is, when your user's browsers invokes the CSHS and the browser includes an expired LTPA cookie, it will be treated as if it was an "initial" request: The TAI kicks in, does whatever you programmed it to do, establish a new authentication, complete the CSHS.
     


    Original Message


Related Content