Add OIDC Redis Token State Manager extension

[michalvavrik]

• closes: Introduce quarkus-oidc-redis-token-state-manager #44382

[github-actions]

🙈 The PR is closed and the preview is expired.

[cescoffier]

I've added a small comment about the Redis key name.

Now, I'm wondering about the future. I was planning to extract Redis to a QV repository. I believe this will come with it (as well as the cache implementation). It's not planned for "now", but something for the future.

[Ladicek]

LGTM, but see the question by @cescoffier

[michalvavrik]

Now, I'm wondering about the future. I was planning to extract Redis to a QV repository. I believe this will come with it (as well as the cache implementation). It's not planned for "now", but something for the future.

There is only a couple QV projects I'd use in production. I think you or Sergey needs to decide this because moving it will come with a price. You won't have to just test and release this OIDC Redis extension with every Quarkus release, but also with every QV Redis release. This way, you will have matching tested version for every Quarkus/Redis/OIDC combination. I just checked OIDC Proxy extension in QV and I don't think things are automated in QV side (though I know next to nothing about Quarkiverse). If that will need to be maintained manually, it will be extra work. Maybe you could move it into shared QV project with Redis?

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit c3440a4.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[sberyozkin]

Thanks @michalvavrik, very neat and simple, thanks @Ladicek for the review

[sberyozkin]

@calvernaz, FYI

[sberyozkin]

Hi @michalvavrik @cescoffier
Apologies I missed the conversation about possible moving of Quarkus Redis Client to Quarkiverse. Yeah, we'll need to decide if the OIDC extension which depends on Redis Client will have to follow it and go to Quarkiverse itself, or may be, we should use this opportunity and figure out how Quarkus externsions living in the main repository can work together with Quarkiverse extensions... Otherwise, if this extension also moves, it is unclear if we have it supported at the product level... It will be an interesting discussion :-)

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit c3440a4.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging/deployment

✖ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

• Expecting actual: ["-4","-5","-6","-7","-8","-9","-10","-11"] to start with: ["-3", "-4", "-5", "-6"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-4","-5","-6","-7","-8","-9","-10","-11"]
to start with:
  ["-3", "-4", "-5", "-6"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:36)