Auth0 Java SDK 5.0.0
This release includes one breaking change that is mechanical to migrate, along with new Management API support for Keys Network ACLs, third-party client access, and Cross-App Access.
🚀 What's New
Keys Network ACLs
Added a new keys().networkAcls() sub-client with support for: List/Create/Get
These operations target:
/api/v2/keys/network-acls
Third-Party (3P) Client Access
Added third_party_client_access to the my_organization_configuration object on clients.
Supported across:
POST /clientsGET /clientsGET /clients/{id}PATCH /clients/{id}
Cross-App Access (XAA)
Added cross_app_access_resource_app to the connection-profile request/response types and ConnectionProfile.
📌 Breaking Change
Session and Refresh-Token Timestamp Getters
Session and refresh-token timestamp getters now return OptionalNullable<T> instead of Optional<T>.
The API declares these fields as nullable, and the SDK now reflects that.
v4:
Optional<SessionDate> created = session.getCreatedAt();v5:
Optional<SessionDate> created = session.getCreatedAt().toOptional();There are also two behavioral changes that may compile silently:
get()now throwsIllegalStateExceptioninstead ofNoSuchElementException.orElse()can now returnnull.
Builder setters are unaffected.
See v5_MIGRATION_GUIDE.md for the complete list of affected getters and step-by-step migration instructions.
📦 Installation
Requires Java 8 or above.
Maven
<dependency>
<groupId>com.auth0</groupId>
<artifactId>auth0</artifactId>
<version>5.0.0</version>
</dependency>Gradle
implementation 'com.auth0:auth0:5.0.0'📖 Resources
| Resource | What it covers |
|---|---|
| v5 Migration Guide | Upgrading from v4 to v5, the breaking change and migration steps |
| README | Overview, installation, and getting started with both APIs |
| Examples | Code samples for common auth0-java scenarios |
| Reference | Code samples for every Management API endpoint |
| Changelog | Full release history |
💬 Feedback
We’d love to hear your feedback! Join the discussion or open an issue on GitHub