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.

ORDS 24.2, Tomcat, Error 571 - Database Connection Error

sharatsinghJan 17 2025 — edited Jan 17 2025

Hi All,

I am getting this error message:

Database Connection Error
HTTP Status Code: 571
ORDS was unable to make a connection to the database. This can occur if the database is unavailable, the maximum number of sessions has been reached or the pool is not correctly configured. The connection pool named: |default|lo| had the following error(s): java.nio.file.AccessDeniedException: /opt/oracle/product/23ai/dbhomeFree/network/admin/tnsnames.ora

I am able to deploy with ORDS jetty server. But, when I tried to deploy with tomcat 9, it is giving this error.

Screenshot 2025-01-17 at 2.41.56 PM.png

This post has been answered by sharatsingh on Jan 27 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 Jan 17 2025
7 comments
296 views