Access Token Verifier Builder fails to initialize

[okta]

Access Token Verifier Builder fails to initialize

[patrick-m-m]

@briangindek I believe I've seen something similar when failing to include the okta-jwt-verifier-impl dependency. I'm not sure what the Ant syntax would be, but for Maven, you have to include both in the pom.xml.

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

[arvindkrishnakumar-okta]

@briangindek Is this still an issue? I am unable to reproduce this in the latest version of the library (0.5.7).

[briangindek]

Yes it is still happening for me. Everything complies ok but when I got to validate a token using the above code I get the above error: java.util.ServiceConfigurationError: com.okta.jwt.AccessTokenVerifier$Builder: Provider com.okta.jwt.impl.jjwt.JjwtAccessTokenVerifierBuilder not a subtype

[briangindek]

I'm using the Okta-jwt-verifier-0.5.8-SNAPSHOT.jar (from api target) when compiling/deploying my java code and using the Okta-jwt-verifier-impl-0.5.8-SNAPSHOT.jar in my execution environment (which happens to be JBoss)

[briangindek]

Since my Jboss build is an ant build, could this simply be caused by me not including a required, dependent jar? Seems like an odd error message for such an issue, but some error messages can be quite misleading.

[rcollette]

Should the waiting for response label be removed at this point?

[arvindkrishnakumar-okta]

Closing this due to inactivity for long, feel free to reopen if further followup is needed.