Forum Discussion
how to have F5 APM send a 401 status code back instead of a 200 for the failed oAuth login attempts
Hi
Yep that is normal. Once the session is established you do not go though it again.
Maybe try to kill the session as well after the RESPOND
ACCESS::session removeLike this the authentication will need to be redone at next attempt
Or try to switch to per request policy ?
Let us know how it goes
It works with the ACCESS::session remove, thanks for the help 😊 .
I would want to use the session for this instead of request, as per-request would cost more to authenticate users with azure on every attempt, which is not a requirement presented to us so far.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com