Uploaded image for project: 'Red Hat build of Keycloak'
  1. Red Hat build of Keycloak
  2. RHBK-2379

New Realm Group should be checked if the name already exists to prevent from a database ERROR log message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 26.0.6
    • source/customers
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      reproducer is simple, use a vanilla RHBK 26.0.6 run in dev-mode with the temporary admin user and create the same realm twice.

      Show
      reproducer is simple, use a vanilla RHBK 26.0.6 run in dev-mode with the temporary admin user and create the same realm twice.

      If a new real is created with a conflicting name the UI will show a message but there is also an ERROR with the full SQL and stacktrace within the logfile.

       

      The expected behavior is that there is no full log at ERROR level as this could be a user concern. It is a simple user mistake to use a existing realm name, so there should be only a message in UI or other API but not a DB ERROR.

              Unassigned Unassigned
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: