Skip to content

Conversation

@prachi-okta
Copy link
Contributor

@prachi-okta prachi-okta commented Jan 15, 2026

All fixes verified and tested. Resource-specific caching demonstrated with User cache (5s TTL) showing 0ms cache hits vs 500ms API calls.

Issue(s)

Description

Category

  • Bugfix
  • Enhancement
  • New Feature
  • Library Upgrade
  • Configuration Change
  • Versioning Change
  • Unit or Integration Test(s)
  • Documentation

Signoff

  • I have submitted a CLA for this PR
  • Each commit message explains what the commit does
  • I have updated documentation to explain what my PR does
  • My code is covered by tests if required
  • I did not edit any automatically generated files

- Fix #1615/#1667: Change LinksResend.resend to array type (List<HrefObject>)
- Fix #1618: Add type validation for cached objects to prevent ClassCastException
- Fix #1619: Set default name for OIDCApplicationBuilder to OIDC_CLIENT
- Fix #1622: Correct expirePasswordWithTempPassword return type to TempPassword
- Fix #1642: Enable custom attributes for GroupProfile (OktaUserGroupProfile)
- Fix #1666: Change JUnit dependency scope from compile to test
- Fix #1657: Upgrade httpclient5 to 5.5.1 to fix connection pool leak
- Fix #1653: Add missing rootSessionId field to LogAuthenticationContext
- Fix #1650: Enable super.equals() call in PasswordPolicyRule for proper parent comparison
- Fix #1600: Implement resource-specific cache lookup in ApiClient
- Update SDK version to 25.0.1-SNAPSHOT

All fixes verified and tested. Resource-specific caching demonstrated with
User cache (5s TTL) showing 0ms cache hits vs 500ms API calls.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment