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

Cannot use access swagger-ui console using RHBQ 2.2.3

XMLWordPrintable

      Issue description: 

      Swagger-ui console not accessible with RHBQ 2.2.3

      With Quarkus 2.2.3, it is not possible to access to swagger-ui console.

      Swagger-ui consoel is accessible with Quarkus community build 2.6.3

      Steps to reproduce
      ==================

      RH-SSO configuration
      =====================

      1. Download and install a Keycloak (16.1.1) or RH-SSSO (7.5.0) instance.

      2. Start keycloak on port 8087

      sh standalone.sh -Djboss.socket.binding.port-offset=7

      3. create realm hoduflu, and import hoduflu-realm.json

       

      Part II -  Swagger-ui working example (using quarkus 2.6.3)
      ============================================================

      Unzip quarkus-secured-swagger-ui-working-example using quarkus 2.6.3

      start quarkus project

      mvn quarkus:dev

      Connect to swagger-ui console using http://localhost:8080/q/swagger-ui

      ===> It is possible to access to teh swagger-ui console, and test /hello resource example.

       

       

      Part III  - Swagger-ui Non working example (using RHBQ 2.2.3)
      =============================================================

      Unzip quarkus-secured-swagger-ui-not-working-example

      start quarkus project

      mvn quarkus:dev

      Connect to swagger-ui console using http://localhost:8080/q/swagger-ui

      ===> You get a blank page, nothing is displayed.

       

       

      This example showcase that swagger-ui is not working/accessible with the attached example for RHBQ 2.2.33, whereas it is working fine with 2.6.3

            pkruger@redhat.com Phillip Krüger
            rhn-support-orivat Olivier Rivat
            Fedor Dudinskii Fedor Dudinskii
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: