[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=13803142#comment-13803142 ] 

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

This particular bug surfaces quite a lot when using WildFly (at least version 17) together with KeyCloak, and makes token exchange fail. While the fixed Elytron implementation is not yet available (right ?) as a WildFly module I wonder which approach would be the better one to workaround the exception stack trace for the current Bearer Token Authentication Mechanism:

# Make a configuration change to Wildfly to use the correct factory class (and if so - how?)
# Create a custom Provider by extending the existing provider and overriding/correcting the default implementation. That custom provider must be configured to replace the existing one... and how is that done?

> 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)