Session State Name Issue

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version affected: 8.2 and older

    Description: When 2 realms are starting with the same number, and they’re both set to “Display Time Out” on the Display TimeOut Message field, users will get redirected to the TimeOut.aspx page instead of the SecureAuth.aspx page even though they have not timed out.

    Cause: Bug in the SecureAuth.aspx.vb file.

    Resolution: Change the Session State Name field values in the workflow tab from their default values, making sure that each Session State Name is unique to each realm.

    0 out of 0 found this helpful



    Please sign in to leave a comment.