Issues with `quarkus-oidc-redis-token-state-manager`

[Jaland]

Describe the bug

Native Image Issues with OIDC Redis Token State Manager

Summary

The quarkus-oidc-redis-token-state-manager seems to be having some issues with Native Builds (but works fine with normal JVM).

Create a repo with some example code that is breaking

Initially, the native image failed to start. After applying changes from this commit, the application now starts but gets stuck in an infinite redirect loop. When the OAuth server redirects back to the application, the application immediately redirects back to the OAuth server.

Environment

• Quarkus Version: 3.26.3
• Java Version: 17
• Build Tool: Maven 3.8+
• OS: Linux (tested on Fedora 42)
• OAuth Provider: Google OAuth 2.0
• Token Storage: Redis 7

The OIDC Redis token state manager should work in native images without requiring:

• Manual reflection registration for internal classes
• Jackson workaround flags
• Additional build arguments

These should be automatically handled by the extension when building native images.

Additional Context

This issue makes the quarkus-oidc-redis-token-state-manager extension unusable in production native deployments. The authentication loop suggests that token serialization/deserialization in Redis may not be working correctly in native images, even with the attempted reflection configuration.

The fact that the same configuration works perfectly in JVM mode indicates this is specifically a native image compatibility issue within the OIDC Redis integration.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Mandrel or GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @Karm (native-image), @Ladicek (redis), @cescoffier (redis), @galderz (native-image), @machi1990 (redis), @pedroigor (oidc), @sberyozkin (oidc), @zakkak (native-image)

[michalvavrik]

I'll have a look at the reproducer today and if it is something about native-image that I can't solve, I'll report back.

[sberyozkin]

Thanks @michalvavrik

[sberyozkin]

@Jaland Thanks for creating the reproducer and trying to make it work in native.

[Jaland]

Thanks y'all.

I will keep an eye on this and let me know if there is anything I can do to help

[michalvavrik]

+1 on thanks, I remember I didn't find suitable IT module in Quarkus project so this is result of it. I can reproduce the issue and know how to fix it (I think, let's see), I am only looking for non-intrusive way to add IT to this project. I should have a time to do it today.

[michalvavrik]

I have added backport labels to #50333, therefore it should get to 3.28 and 3.27 eventually, but you will still have to watch the PR / issue milestone as to when it got backported. Here is a release planning in case you don't know about it - https://github.com/quarkusio/quarkus/wiki/Release-Planning.

It fixes the cause of your failures. I dropped https://github.com/Jaland/quarkus-oidc-redis-cache-example/tree/main/src/main/resources/META-INF/native-image, https://github.com/Jaland/quarkus-oidc-redis-cache-example/blob/f04997506aeba368576e7005998ed1cc4b631022/src/main/resources/application.properties#L28 and https://github.com/Jaland/quarkus-oidc-redis-cache-example/blob/f04997506aeba368576e7005998ed1cc4b631022/src/main/resources/application.properties#L29C3-L29C4 when testing your reproducer as it creates a lot of mess, but it is not really related, you can do whatever your application needs.