[pushkala-datastax]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-20059179	710	com.yahoo.athenz:athenz-zpe-java-client: 1.10.50 -> 1.12.49 No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[pushkala-datastax]

The upgrade from version 1.10.50 to 1.12.49 crosses a major breaking change boundary at version 1.11.0.

Key Breaking Changes in v1.11.0:

• Java 11 Required: The library now requires Java 11 or later, a jump from the previous requirement of Java 8.
• Namespace Migration: The library has migrated from javax to the jakarta namespace as part of its upgrade to Jetty 11.x.
• HTTP Client Rewrite: The ZMS and ZTS Java clients have been rewritten to use the Apache HTTP Client directly, removing the previous dependency on jax-rs and jersey. This change is likely to impact how HTTP clients are instantiated and configured.

Recommendation:
This upgrade requires significant developer action. Before merging, you must:

1. Ensure your project is running on Java 11 or a later version.
2. Update your code to use the jakarta namespace instead of javax where it interacts with this library.
3. Review your client instantiation and configuration code to adapt to the new Apache Http Client implementation, replacing any Jersey-specific logic.

Source: Athenz Release Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.