Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-7178

Encrypt OIDC tokens for custom TokenStateManager implementations

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.33.0.GA
    • None
    • None
    • None

      Fixes #51083.

      This PR ensure that by default, tokens are encrypted by default irrespective of whether it is a `default` `TokenStateManager` or a custom one.

      It lets the default one to continue encrypting tokens itself, because it encrypts the session cookie that holds all tokens, with a few tests proving it.

      DB `TokenStateManager`, which is a custom `TokenStateManager`, is tested to prove it has tokens encrypted by default but also that users retain an option to avoid encrypting them. I run most of DB tests including the optional ones, `Db2DB` was the only one I could not run as the image download takes ages and probably hangs...

      I did not update Redis `TokenStateManager` tests because it is just another custom `TokenStateManager`.

              msochure@redhat.com Miroslav Sochurek
              msochure@redhat.com Miroslav Sochurek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: