[ https://issues.jboss.org/browse/ELY-1847?page=com.atlassian.jira.plugin.s... ] 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? -- This message was sent by Atlassian Jira (v7.13.8#713008)