A complete, runnable guide to OCI and Entra token files and SDK suppliers, JDBC providers and connection pools—with database setup and Microsoft Entra identity configuration.

Cloud identity, database mapping, TLS and token lifecycle work together to authenticate each new physical connection.

Key Takeaways

Run the same read-only Java application with OCI or Entra token files, application-owned SDK suppliers, or JDBC providers.

Database trust, principal-to-schema mapping, cloud authorization and TCPS must all agree before a token login can succeed.

The repository contains complete source, configuration profiles including native JDBC properties files, SQL setup templates, concurrent UCP examples and automated tests.

Verify token refresh with newly created physical connections; reusing an existing pooled session does not prove that refresh works.

A Java application can authenticate to Oracle AI Database with an OCI IAM or Microsoft Entra ID token instead of passing a database password.…