Invalid State Error? - How to fix it in ISAM

Contents

• Overview
• Runtime Tuning Parameters
• Additional Information/Links

Overview

When interacting with federation partners in Verify Access and ISAM, we create an /authorize request off to that identity provider with a state ID. If the user spends more than 10 minutes authenticating with the Identity Provider, then when they return back, we might get the following error FBTOIC106E Invalid state from the runtime.

This error can mean multiple things, but in this case, it most likely that the runtime session has expired. So, how can we extend this?

Runtime Tuning Parameters

There are two key settings we can change to help address this error.

Session Invalidation Timeout:
This parameter defines the amount of time a session can remain unused before it is no longer valid. The default setting is 600 seconds.

1. On the Runtime Tuning Parameters panel, select Session Invalidation Timeout.
2. Click Edit.
3. In the Session Invalidation Timeout window, define the value in seconds.
4. Click OK.

Maximum Session Count:
This parameter defines the maximum number of sessions that is maintained in memory. The default setting is 250,000 sessions.

1. On the Runtime Tuning Parameters panel, select Maximum Session Count.
2. Click Edit.
3. In the Maximum Session Count window, define the value.
4. Click OK.

Additional Information/Links

Here are some useful links you can checkout for additional information.

• HTTP Session Management