Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-543

Airbrake caused by using HTTP protocol in RH-SSO integration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 2.1 GA, SaaS
    • System
    • +
    • Hide

      Configure RH-SSO with HTTP endpoint: *http://localhost:8080/auth/realms/myrealm*

      Try to test the authentication flow after configuring RH-SSO and 3scale according to tutorial

      Login will be successful on the SSO server but you will receive Something went wrong internal error error message on the callback.

      Show
      Configure RH-SSO with HTTP endpoint: * http://localhost:8080/auth/realms/myrealm* Try to test the authentication flow after configuring RH-SSO and 3scale according to tutorial Login will be successful on the SSO server but you will receive Something went wrong internal error error message on the callback.

      Following Airbrake is triggered when the RH-SSO endpoint is HTTP:

      [multitenant] Production Faraday::ConnectionFailed: Failed to open TCP connection to 127.0.0.1:443 (Connection refused - connect(2) for "127.0.0.1" port 443)
      

      System forces an HTTPS connection after the callback even though an HTTP endpoint is configured. If the domain is not exposed on port 443 then the token request will fail. This should connect over the configured protocol in the SSO integration page.

        1. 1.png
          1.png
          203 kB
        2. 2.png
          2.png
          348 kB
        3. 3.png
          3.png
          403 kB
        4. 4.png
          4.png
          841 kB
        5. admin-portal.png
          admin-portal.png
          168 kB
        6. keycloak.png
          keycloak.png
          201 kB

            Unassigned Unassigned
            rhn-support-keprice Kevin Price
            Guilherme Cassolato Guilherme Cassolato
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: