Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-7703

PathBasedKeycloakConfigResolver - more generic behavior

    Details

    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      KEYCLOAK-7523 made PathBasedKeycloakConfigResolver more consistent, but I have another solution - given full path like /a/path/to/some/servlet we can start with checking if etc/a-path-to-some-servlet-keycloak.json exists and if not, checking etc/a-path-to-some-keycloak.json ending with totally generic, fallback etc/keycloak.json.

      The dilemma I had with servlets registered to default context (like CXF servlet registered under / context path and /cxf servlet path) was that we usually don't want single etc/cxf-keycloak.json configuration to cover all CXF applications (endpoints), so next (deeper) path segment may be used to select more specific Keycloak configuration.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  hmlnarik Hynek Mlnařík
                  Reporter:
                  grgrzybek Grzegorz Grzybek
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: