We have a java SDK (okta-sdk-java), version 8.2.0 and auth sdk (okta-auth-java), version 2.0.7
Java SDK has been retired, and we’d like to upgrade to version 10.1.3.
However, seems like auth (even the newest version, 3.0) still uses Java SDK 8.2.5.
This makes upgrading the Java SDK to 10.1.3 impossible. How can we work around that? Is there something we are missing?
You can create a shadow JAR that bundles the necessary dependencies together, ensuring that there are no conflicts. This approach is more complex but can be effective for resolving deep dependency conflicts.
OR
You can exclude the older version of okta-sdk-java that okta-auth-java depends on and force the use of the newer version. This can be done in your pom.xml if you are using Maven, or in your build.gradle if you are using Gradle.
com.okta.sdk
okta-auth-java
3.0.0
com.okta.sdk
okta-sdk-java
com.okta.sdk
okta-sdk-java
10.1.3
The simplest and most common approach is using dependency exclusion to force the use of the newer SDK version. If this method does not resolve your issue, consider contacting Okta support for guidance or exploring more advanced options like shadow JARs or forking and modifying the SDK. more help…
Creating a single large JAR wouldn’t really work - I would need to run it in a different service, which I prefer to avoid.
And I would also hate changing your code, even if it’s open sourced…
Any other alternatives? Are you not aupporting the authn solution anymore?