I was watching a fiddler trace when calling /AGLogout against a protected resource on the AG.
I see first a GET for
That results in a 200, as expected.
Next I see a GET request for
Which normally results in a 302 redirect on most of the systems I checked.
However, I'm seeing on one system that this is resulting in a 404 not found and sometimes the end user gets left on that broken page. I'm trying to figure out why this happens in this one configuration.
All the systems I looked at are 220.127.116.11 running on SLES 12 SP5. All the systems I have compared to work properly and result in a 302 redirect. Some have mobile access enabled and some do not.
So my questions are...
1. How does this even work at all calling /nidp/mobileaccess from the AG (IdP is NOT proxied)?
2. How do I fix my broken system?