[jboss-jira] [JBoss JIRA] (ELY-1847) WildFlyElytronProvider Loading wrong class for Bearer

[Lennart Jörelid (Jira)]

    [ https://issues.jboss.org/browse/ELY-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803281#comment-13803281 ] 

Lennart Jörelid commented on ELY-1847:
--------------------------------------

Seems to be a good solution for when Keycloak supports Wildfly 18. 

Until then, however, we have to run on top of Wildfly 17, which basically refuses to accept the token emitted by Keycloak 7.0.1 (latest release). Since the fix is not too complex, we only need to know how to configure the Elytron subsystem to use a custom provider for the Bearer Token Authentication mechanism.

Or would you recommend installing Elytron 1.10 on top of Wildfly 17 instead?


> WildFlyElytronProvider Loading wrong class for Bearer
> -----------------------------------------------------
>
>                 Key: ELY-1847
>                 URL: https://issues.jboss.org/browse/ELY-1847
>             Project: WildFly Elytron
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>            Priority: Critical
>             Fix For: 2.0.0.Alpha5, 1.10.0.CR4
>
>
> {noformat}
> Caused by: java.lang.NoSuchMethodException: org.wildfly.security.http.bearer.BearerTokenAuthenticationMechanism.<init>(java.security.Provider)
>     at java.lang.Class.getConstructor0(Class.java:3082)
>     at java.lang.Class.getConstructor(Class.java:1825)
>     at org.wildfly.security.WildFlyElytronProvider$ProviderService.newInstance(WildFlyElytronProvider.java:339)
> {noformat}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)