Uploaded image for project: 'RH-SSO'
  1. RH-SSO
  2. RHSSO-2251

Unable to set "Backchannel logout URL" through Keycloak API

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • None
    • None
    • None
    • False
    • None
    • False

    Description

      rhsso: registry.redhat.io/rh-sso-7/sso76-openshift-rhel8 or Keycloak 20

       

      I am trying to automate a "back channel logout" scenario with Quarkus over OpenShift. The main problem that I am facing is that Keycloak needs an application endpoint in order to do the logout callback once the logout is triggered, but also the application needs the Keycloak URL in order to be deployed. To me, the "easiest" approach would be to deploy Keycloak without a "back channel logout path" and then once the application is also deployed, set the "back channel logout path" from the test itself (maybe in the tear-up). 

      Steps

      1. deploy Keycloak
      2. deploy Quarkus application pointing to the previously deployed Keycloak
      3. Set up "back channel logout path" from the test, based on the previous app deployment. 

      But, I could not find any admin API that allows me to set this Client configuration. 

      Do you know if currently we are supporting this feature? , or do you have any better idea in order to set up this scenario in Openshift? 

      Thanks in advance, 

       

      cc psilva@redhat.com sbiarozk 

      Attachments

        Issue Links

          Activity

            People

              sthorger@redhat.com Stian Thorgersen
              rh-ee-mvavrik Michal Vavrik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: