We are not sure if this is expected behavior or actually something we need to address.
- Go to the AM Login page in AM 6 or 6.5:
- Clear cookie cache: chrome://settings/clearBrowserData
- Open DevTools (ctl+shft+i).
- Refresh the page and observer the workflow (see screenshot).
If a token exists, then these pass with Status Code 200.
Info from a discussion (between Todd and Phil) via casework.
The use case behind this call is more complex, but one of the main reasons for this call is for detecting a realm change. Previously in the UI, realms could be changed without reloading the application so there had to be a detection system for this. The UI now requires a refresh, so this use-case no longer exists, however there is legacy code still operating on this assumption. The double calls upon boot, I’ve not investigated as yet.