Forum Discussion
If you see the VPE above, after AD auth, it goes to MACRO, which actually is 2nd Level Auth. So After AD auth, User is actually redirected to the External Logon Page and everything works fine. The issue here is that the F5 is sending 200 OK after AD Auth before going to 2nd level auth, but user want it should be 302, because of some "security audit" purposes.
As I said, everything is working fine, but just needs to see why F5 responds with 200 OK if 2nd Level HTTP AUTH is in place and is there a way to change it???
If you remove HTTP Auth, from the flow, F5 responds with 302 and takes you to app. which is fine. So the question here is regarding the 200 OK that comes after AD AUTH......
See my HTTP watch output for a lab scenario, where I remove the 2nd level auth and I get 302 while posting on /my.policy