@RaymondBrodeur (Customer)​.

This is not currently listed in the RSA Authentication Manager 8.9 Known Issues article. I am checking to see if there is a tracked defect for the symptoms you are reporting.

Things to check in the meantime:

• From the Operations Console, flush all cached objects.
• From the Security Console, open Console & Session Settings, confirm the values are still what you expect after the patch, and click Save again.
• Check whether the affected administrators have their own session lifetime settings. These can override the system defaults.
• If a load balancer or proxy sits in front of the Security Console, check whether its idle or session timeout is shorter than the AM setting.

If this affects your operations, please also open a support case. We will need the following details from you:

• The idle timeout and maximum session lifetime values set in Console & Session Settings.
• Roughly how long administrators stay signed in before the console signs them out.
• The difference between this number and what the timeout was before you installed patch 5.
• Whether this happens only when the session is idle, or also while administrators are working in the console.
• Whether it happens on the primary, the replicas, or both.
• Whether administrators reach the Security Console directly or through a load balancer, reverse proxy, or web tier.
• The browser and version you're using.
• Enable verbose logging on your primary and all replicas then have behavior happen. Generate troubleshooting log bundles for review and attach them to the case.

Best regards,

Erica