When logging in via AMS (with PIV), after the authentication is complete, there is what appears to be a 1-5 second delay before the home page displays

Expected Behavior

The delay between completing the authentication process and getting redirected to the correct OPS environment landing page should be more reasonable.

Current Behavior

The homepage doesn't render for about 1-5 seconds after the AMS authentication is seemingly complete. Instead, the user is taken back to the same screen they saw before auth to AMS ever occurred and they think they need to repeat the login action again--causing further issues due to only active session being permitted.

Possible Cause

Waiting on AMS for the last round trip call being made without any visual indication of the user to wait for the authn process to complete.

Steps to Reproduce

1. From GFE, navigate to the Azure dev, staging, or prod environment URLs.
2. Choose the option to log in with HHS AMS presuming you have a valid user created and ready for you in the DB.
3. Observe the delay before the OPS home page is returned.

See the recording of the 02/20/2025 meeting starting at 28:33 for the experience captured in production

Context

This is not the same as the ACA cold start delay, which is far longer and is seen on the first login or real application activity following a new deployment.

Possible Implementation

Display a spinner or separate splash page while we wait for the token to come back from AMS. We would also want some kind of safety condition to kick in though to avoid a scenario of the user getting stuck on the spinner forever if something did go wrong.

See

Possible UI improvements to not disorient users:

• https://github.com/davidhu2000/react-spinners
• https://www.davidhu.io/react-spinners/storybook/?path=/docs/pacmanloader--docs