[PR #5024/88a3daf2 backport][stable-5] Fix: Add user-agent header to allow request through WAF with bot protection #5046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #5024 as merged into main (88a3daf).
SUMMARY
When keycloak is running behind WAF or CDN, (.e.g Cloudflare with DNS Proxy) Requests with no User-Agent get status code 403 Forbidden.
Fixes #5023
ISSUE TYPE
COMPONENT NAME
module_utils/identity/keycloak
ADDITIONAL INFORMATION
When Keycloak is running behind a CDN/WAF, absence of use-agent gets considered as bot request and hence return 403 Forbidden
Before Change
After Change