Accessing the request URI in Authenticator fails at runtime #10628

CollinAlpert · 2022-03-07T15:59:29Z

CollinAlpert
Mar 7, 2022

I have a custom Authenticator SPI and in the authenticate method I need to access the request URI. If I call context.getHttpRequest().getUri(), the following exception is thrown when the Authenticator is run:

Uncaught server error: 
java.lang.NoSuchMethodError: 'org.jboss.resteasy.spi.ResteasyUriInfo org.jboss.resteasy.spi.HttpRequest.getUri()'

These are my dependencies:

<dependency>
    <groupId>org.keycloak</groupId>
    <artifactId>keycloak-services</artifactId>
    <version>${keycloak.version}</version>
    <scope>provided</scope>
</dependency>
<dependency>
    <groupId>org.keycloak</groupId>
    <artifactId>keycloak-server-spi</artifactId>
    <version>${keycloak.version}</version>
    <scope>provided</scope>
</dependency>
<dependency>
    <groupId>org.keycloak</groupId>
    <artifactId>keycloak-server-spi-private</artifactId>
    <version>${keycloak.version}</version>
    <scope>provided</scope>
</dependency>

What am I missing? I am using Keycloak 17 (both in server and Maven dependencies)

ariel-adler · 2022-03-09T18:34:24Z

ariel-adler
Mar 9, 2022

It also happens in version 16.1.1
Any idea?

4 replies

CollinAlpert Mar 9, 2022
Author

I have found it to be related to #9599 (specifically this comment). You can see if one of the solutions posted there will help you.

ariel-adler Mar 10, 2022

Thank you Collin it works :)

Add this to maven:

     <properties>
         <resteasy.version>4.7.4.Final</resteasy.version>
    </properties>

    <dependency>
        <groupId>org.jboss.resteasy</groupId>
        <artifactId>resteasy-client</artifactId>
        <version>${resteasy.version}</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>org.jboss.resteasy</groupId>
        <artifactId>resteasy-jackson2-provider</artifactId>
        <version>${resteasy.version}</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>org.jboss.resteasy</groupId>
        <artifactId>resteasy-multipart-provider</artifactId>
        <version>${resteasy.version}</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>org.jboss.resteasy</groupId>
        <artifactId>resteasy-jaxb-provider</artifactId>
        <version>${resteasy.version}</version>
        <scope>provided</scope>
    </dependency>

CollinAlpert Mar 10, 2022
Author

Actually I have found that adding only resteasy-multipart-provider works as well.

ariel-adler Mar 10, 2022

Good to know.
Thank you!

fzoli · 2022-03-16T08:42:30Z

fzoli
Mar 16, 2022

8000

For me the provided dependency does not solve the problem.
I build a flat JAR with Gradle. In this build system provided means that the library is used only at compile time, but it is not part of the flat JAR.

Anyway I found a workaround:

I replaced context.getHttpRequest().getUri().getQueryParameters() to context.getSession().getContext().getUri().getDelegate().getQueryParameters()

1 reply

jamesdh Jan 25, 2023

We're on version 15 still and we started seeing this recently. Not entirely sure where the dependency change came from since we haven't touched anything. In any case, @fzoli's solution appears to work regardless of the version of resteasy that is used.

Navigation Menu

Repository navigation

Accessing the request URI in Authenticator fails at runtime #10628

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Accessing the request URI in Authenticator fails at runtime #10628

Uh oh!

CollinAlpert Mar 7, 2022

Replies: 2 comments · 5 replies

Uh oh!

ariel-adler Mar 9, 2022

Uh oh!

Uh oh!

CollinAlpert Mar 9, 2022 Author

Uh oh!

ariel-adler Mar 10, 2022

Uh oh!

CollinAlpert Mar 10, 2022 Author

Uh oh!

ariel-adler Mar 10, 2022

Uh oh!

fzoli Mar 16, 2022

Uh oh!

jamesdh Jan 25, 2023

CollinAlpert
Mar 7, 2022

Replies: 2 comments 5 replies

ariel-adler
Mar 9, 2022

CollinAlpert Mar 9, 2022
Author

CollinAlpert Mar 10, 2022
Author

fzoli
Mar 16, 2022