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.

OAuth PL/SQL - rexpiry of the client secret?

schubefrJan 18 2025 — edited Jan 20 2025

I have been registered a Client by using OAUTH.CREATE_CLIENT

Is there an experation date of the client secret? Is the client secret automaticaly updated?

Additional findings:

Not only the secrets have been changed, but the client also IDs too.

The strange, the updated_on in the table user_ords_clients wasn't update.

How can that happen?

Thanks for support

Frank

PS: ORDS Version is 20.1

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 18 2025
2 comments
155 views