IBM Security Verify

 View Only
  • 1.  FBTAUT004E Authentication service receives invalid state ID

    Posted Mon October 26, 2020 09:54 AM
    ​Hello
    We have ISAM Webseal 9.0.7.0 (EAI) + AAC (INFOMAP)
    We implemented FormBased authentication using INFOMAP Mechanism and sometimes the user gets an error during authentication
    "FBTAUT004E Authentication service receives invalid state ID [db3688c0-5d89-4414-b4a1-8af0cf330f4f]. Ensure that you do not use back button on the browser or perform multiple authentication processes in the same browser. Please re-access the protected resource"

    Is there an easy way to fix this error?

    ------------------------------
    Ivan Goncharov
    ------------------------------


  • 2.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Mon October 26, 2020 11:27 AM
    Hi Ivan, I afronted the same issue some months ago, what helped me was modifying my login html page to automatically refresh itself every minute.
    I hope it helps you too.
    Regards.

    ------------------------------
    David Vicenteño
    ------------------------------



  • 3.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Tue October 27, 2020 08:47 AM
    David, can you tell in more detail ?


    ------------------------------
    Ivan Goncharov
    ------------------------------



  • 4.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Wed October 28, 2020 11:22 AM
    Edited by David Vicenteño Wed October 28, 2020 11:28 AM
    What worked for me was inserting a meta tag for refresh my infomap login html page.
    Sample:
    infomaploginpage


    I hope this help you too.
    Regards.


    ------------------------------
    David Vicenteño
    ------------------------------



  • 5.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Tue October 27, 2020 09:38 AM
    Hi,

    We are facing the exact same issue and currently have a PMR up for this.

    We are using a workaround in our QA environment that works. But it can give an potential issue with stale cookies according to IBM.
    - In WRP Configuration:
    #managed-cookies-list = *ac.uuid,*JSESSIONID*
    managed-cookies-list = *ac.uuid

    David: Could you elaborate how this solved the issue? Any help is appreciated.

    Regards,
    Tony

    ------------------------------
    Tony Larsson
    ------------------------------



  • 6.  RE: FBTAUT004E Authentication service receives invalid state ID

    IBM Champion
    Posted Mon February 01, 2021 04:25 PM

    Hi Tony – Is there anything valuable (remediation, configuration, custom code, etc) that came out of the PMR opened with IBM on this subject to handle more gracefully authsvc invalid state ID messages ? Besides what has been shared so far on this discussion thread.



    ------------------------------
    Sylvain Gilbert
    ------------------------------



  • 7.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Tue February 02, 2021 03:15 AM
    Hello Sylvain,

    Sadly no. The PMR is still ongoing and L3 is currently investigating.

    Our workaround seems to work for now at least, as we have not heard of any problems from end-users.

    Regards,
    Tony

    ------------------------------
    Tony Larsson
    ------------------------------



  • 8.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Thu February 11, 2021 03:10 PM
    Hi Tony, I am facing the same issue, any fix provided by IBM on this issue?

    ------------------------------
    Venkat
    ------------------------------



  • 9.  RE: FBTAUT004E Authentication service receives invalid state ID

    Posted Thu February 11, 2021 03:26 PM

    Hello Venkat and Others,

    The FBTAUT004E means a few things:
    A) A request was made to the '/authsvc' or '/apiauthsvc' endpoint and contained a StateID that was invalid

     - EG : StateId=blah

    B) A request was made to the '/authsvc' or '/apiauthsvc' endpoint with a valid StateID but it went to a different JVM and you're not sharing sessions between the JVM

    C) A request was made to the '/authsvc' or '/apiauthsvc' endpoint, it has a valid StateID and it went to the same JVM but the JSESSSIOND cookie is missing

    D) A request was made to the '/authsvc' or '/apiauthsvc' endpoint, it has a valid StateID and it went to the same JVM with a JSESSIONID cookie but it's invalid

     - EG: It came from a different app that has the same cookie name


    Resolution to the above

    1) Use the cookieless solution as described here:
    https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.7/com.ibm.isam.doc/config/task/tsk_config_aac_cookieless.html

    2) Change the AAC Cookie name with the following advanced tuning parameter:
    Key : runtime_profile.liberty_option.httpSession.cookieName
    Value : AACJSESSIONID (or anything unique you want to use)

    3) Share JSESSIONID via the DSC with the following advanced configuration parameter:
    https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.7/com.ibm.isam.doc/config/reference/ref_aac_advcfgprop.html#aac_advcfgprop__d179e1910
    distributedSessionCache.enabled = true

    Any and all of these combined make for a more robust implementation of AAC in a clustered environment.



    ------------------------------
    JACK YARBOROUGH
    ------------------------------