Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-3785

[janus-idp/backstage-plugins] Keycloak backend plugin is not working as expected

Create Doc EPIC for Fe...Prepare for Y ReleasePrepare for Z ReleaseXMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Fix undefined value for keycloak group members.
    • Bug Fix
    • 3
    • RHDH Plugins 3263, RHDH Plugins 3264, RHDH Plugins 3265

      [2495986808] Upstream Reporter: Vaibhav Paralikar
      Upstream issue status: Closed
      Upstream description:

      Describe the bug

      I have setup the Keycloak backend plugin by following the steps given on below this link - https://janus-idp.io/plugins/keycloak/ . Plugin configure successfully and it started syncing users and groups, but then abruptly, it stopped syncing with below error.

      Processor BuiltinKindsEntityProcessor threw an error while validating the entity group:default/mainstream-engineering-admin; caused by TypeError: /spec/members/2 must be string - type: string entity=group:default/mainstream-engineering-admin location=url:https://authusqa.devops.sws.company.com/auth/admin/realms/chim/groups/480049ad-7a33-41ab-87a6-382a797831e0

      I am using the new backend and followed the plugin configuration steps accordingly.

      Expected Behavior

      All users and groups from keyclock realm should be synced

      What are the steps to reproduce this bug?

      1. Setup backstage
      2. Configure the Keycloak plugin for new backup configuration (using steps from https://janus-idp.io/plugins/keycloak/)

      Versions of software used and environment

      @janus-idp/backstage-plugin-keycloak-backend": "^1.13.1",

      Backstage - 1.30.4 (create-app@0.5.18)


      Upstream URL: https://github.com/janus-idp/backstage-plugins/issues/2112

              oandriie Aleksander Andriienko
              upstream-sync Upstream Sync
              RHIDP - Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: