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

Correctly restore query params when OIDC does not drop redirect params

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • team/eng
    • None

      Fixes #49225
      Quarkus OIDC can restore the origin request path and query parameters after the user logged in and was redirected back to Quarkus.
      Users can also choose to keep the code flow parameters such as code, state that are included in the redirect URI, and in this case, restoring the original query sequence does not work due to a missing &query parameter separator.
      The test structured as follows - the user logs in, is redirected back to a requested callback, but since the original request URI must be restored, the test callback method fails if it is invoked, instead the method accepting the original URI and query parameter is called.

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

                Created:
                Updated:
                Resolved: