Releases: redis/jvm-redis-authx-entraid
0.1.1-beta2
Changes
Support for DefaultAzureCredentials is now available. Microsoft® Azure Platform offers a streamlined authentication solution for TBA scenarios through a unified construct called DefaultAzureCredentials. This version makes it available for an easier integration with Redis Java Client libraries, Jedis & Lettuce
More details on DefaultAzureCredentials;
https://learn.microsoft.com/en-us/java/api/com.azure.identity.defaultazurecredential?view=azure-java-stable
https://learn.microsoft.com/en-us/java/api/overview/azure/identity-readme?view=azure-java-stable
🚀 New Features
🐛 Bug Fixes
- Fix clone method of AzureTokenAuthConfigBuilder by @atakavci in #19
- Add check for missing IdentityProvider configuration. by @ggivo in #12
🧰 Maintenance
- Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.10.1 to 3.11.2 by @dependabot in #6
- Bump com.microsoft.azure:msal4j from 1.17.2 to 1.19.1 by @dependabot in #16
- Fix cache version in pipeline by @atakavci in #17
- Switch to revelc formatter and format code by @atakavci in #18
- Bump org.awaitility:awaitility from 4.2.2 to 4.3.0 by @dependabot in #24
- Bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.1 to 3.5.2 by @dependabot in #23
- Bump com.azure:azure-identity from 1.15.3 to 1.15.4 by @dependabot in #22
- Bump com.auth0:java-jwt from 4.4.0 to 4.5.0 by @dependabot in #21
Contributors
We'd like to thank all the contributors who worked on this release!
Full Changelog: v0.1.1-beta1...v0.1.1-beta2
0.1.1-beta1
Initial Beta release !!
This is the first beta release of the extension for Redis Java client libraries(lettuce and Jedis) to support token-based authentication.
This initial version provides common classes and interfaces in the core
to build an infrastructure for both;
- making it easy to integrate on both client libraries (Jedis & Lettuce)
- extensibility to provide different identity providers.
As well as core
, it introduces the first implementation to integrate Microsoft EntraID into it with entra
module.
Basic usage would look like this;
TokenAuthConfig tokenAuthConfig = EntraIDTokenAuthConfigBuilder.builder()
.clientId("YOUR_CLIENT_ID").secret("YOUR_SECRET")
.authority("YOUR_AUTHORITY").scopes("SCOPES").build();
With this tokenAuthConfig
provided, clients can build their own way of consuming tokens.