Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Michel.

Asked: September 08, 2025 - 11:43 am UTC

Last updated: September 19, 2025 - 6:45 am UTC

Version: Apex 19.2, bd 19.0

Viewed 1000+ times

You Asked

Hello, I’ve set up Social Login authentication using the Keycloak service.

We’re in a cloud environment hosted on AWS. The AWS WAF is blocking the request that APEX makes for authentication because the request does not contain a User-Agent. I’m getting a 403 error — this is considered a security vulnerability since the request doesn’t come from a browser, from database.

Which would normally include the User-Agent.
Is it possible to configure either APEX, the database or the ORDS service so that the requests they make include the User-Agent information?

It's possible to add default parameter to setting User-Agent for the database request header ?

Otherwise I would have to rewrite the requests at the waf or load balancer level.

and Connor said...

This unfortunately is the price of old software :-)

From APEX *20*, we send user agent details.

But since you're going to be upgrading :-) I'd suggest moving to APEX 24.2