Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Issue: Dependency Resolution for OKTA in Core bundle

Avatar

Level 2

Hello Experts,

 

We are trying to include below dependency in the core package 

<dependency>
   <groupId>com.okta.jwt</groupId>
   <artifactId>okta-jwt-verifier</artifactId>
   <version>${okta-jwt.version}</version>
</dependency>

<dependency>
  <groupId>com.okta.jwt</groupId>
  <artifactId>okta-jwt-verifier-impl</artifactId>
  <version>${okta-jwt.version}</version>
  <scope>runtime</scope>
</dependency>

(version is 0.5.1)

We are seeing below dependency resolution error when the bundle is installed (not activated because of the dependency issue)

 MicrosoftTeams-image (4).png

 

We are using maven bnd plugin and all the other dependencies are resolved without any issue but this. Could you please share your experience if you have encountered this issue before and resolved. Appreciate you time 

 

Okta documentation :

https://developer.okta.com/docs/guides/validate-access-tokens/java/main/ 

 

3 Replies

Avatar

Community Advisor

Hi,

 

Did you check whether the jar is downloaded under .m2 repository folder? If it is not downloaded you can try downloading the jar manually and add to .m2 repository

 

You can check below link for similar issue

 

https://github.com/okta/okta-jwt-verifier-java/issues/43

Avatar

Level 2

@Ravi_Pampana The jar files are downloaded under .m2 folder. Apparently there was no resolution provided by OKTA team at https://github.com/okta/okta-jwt-verifier-java/issues/43

 

Using AEM Archetype 23

Avatar

Employee Advisor

Could you convert these jar files into OSGi bundle as suggested and upload into web console to fix this dependency issue [give a try] -

DEBAL_DAS_0-1647011311552.png

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-17475.html?lang=en [Convert jar into an OSGi bundle].

 

But you have to define Export packages precisely and these export java packages are getting used in your implementation [

  • Export-Package is a list of packages contained in the jar that you would like to make available to other bundles running in the OSGi Container.]