Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

How to log X-FORWARDED-FOR instead of REMOTE_ADDR in apex_workspace_sessions

SashaFeb 1 2025 — edited Feb 1 2025

Hi, guys!

After moving proxing from ajp to http (as ajp is not supported officially by ORDS) we got an IP of proxy not real client in apex_workspace_sessions.remote_addr as APEX seems to get OWA_UTIL.GET_CGI_ENV('REMOTE_ADDR')) but not
OWA_UTIL.GET_CGI_ENV('X-FORWARDED-FOR').

I guess ORDS's settings can change it to log real clients ip (X-FORWARDED-FOR)

Appreciate for Your ideas.

This post has been answered by jariola on Feb 3 2025
Jump to Answer

Comments

thatJeffSmith-Oracle Feb 13 2025

Your ENTRA users will get authenticated via JSON Web Tokens, and their Entra roles will determine which ORDS REST APIs they can hit.

When they hit an endpoint, it'll execute code in the database as the database user that owns the schema where the REST API is defined, not as Entra defiend end user. In fact, the Entra users won't have accounts in the database (they could, but wont' need to).

The :current_user field as far as ords is concerned would be the corresponding oauth2 client or JWT issued for the authorizied session.

Your prehook should be able to alter the session to set the context that would put your RLS/VPD security policy in play.

1 - 1

Post Details

Added on Feb 1 2025
2 comments
138 views