0.0.3

What's Changed

Clock-Skew Validation Enforcement

The clockSkew configuration property now enforces a hard maximum of 60 seconds.
Providing a value above this limit throws an IllegalArgumentException immediately at
configuration time — both via the builder API and via Spring Boot auto-configuration
properties — so misconfigured deployments fail fast rather than silently accepting
an unsafe tolerance.

Behaviour summary

Input	Result
null	Treated as Duration.ZERO (no skew)
0 – 60 s	Accepted and stored as-is
> 60 s	IllegalArgumentException: "clockSkew exceeds the maximum allowed value of 60 seconds"
Negative	IllegalArgumentException: "clockSkew must not be negative"

Affected classes

• TokenValidatorBuilder.clockSkew(Duration) — new MAX_CLOCK_SKEW constant (Duration.ofSeconds(60)) exposed as static final
• TokenValidatorProperties.setClockSkew(Duration) — same enforcement; MAX_CLOCK_SKEW exposed as public static final

---

Dependency Upgrades

Dependency	Previous	Updated
Spring Boot	4.0.6	4.0.7

---

Other Changes

• Update next version by @eclipse-ecsp-bot in #15
• Clockskew validation by @abhishekkumar-harman in #16
• Update DEPENDENCIES by @eclipse-ecsp-bot in #17
• Update DEPENDENCIES by @eclipse-ecsp-bot in #18

New Contributors

• @abhishekkumar-harman made their first contribution in #16

Full Changelog: 0.0.2...0.0.3