Forum Discussion
Downside of using 401 as receive string on health check
do you see any downside of using receive string 401 instead of 200 on the health check monitor. knowing that we decided to go for 401 after having the SSO enabled on the application. so the health check will never return 200.
i am wondering if this has hidden effect
2 Replies
- Stanislas_Piro2
Cumulonimbus
Hi,
Monitor does not use SSO methods configured on APM (I guess you are using APM when talking about SSO)
if your server request 401, you must define a username / password on monitor to authenticate and get 200 status code.
Hi Moussa,
by using a anonymous health-check request and accepting the err401 as a valid response, you can not guarantee that the application throws an err500 after a user logs in.
Beside of that, there shouldn't be any additional down sides...
Cheers, Kai
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