Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-13933 Client Policies
  3. KEYCLOAK-18108

Configuration of executor of incorrect profile is used when two profiles with executor of same type

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 14.0.0
    • Component/s: None
    • Labels:
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      • Create client profile "MyProfile", which has SecureClientAuthEnforceExecutorFactory with configuration, which allows to authenticate with JWTClientSecretAuthenticator.PROVIDER_ID
      • Create client profile "UnusedProfile", which has SecureClientAuthEnforceExecutorFactory with configuration, which does NOT allow to authenticate with JWTClientSecretAuthenticator.PROVIDER_ID . Configuration of both profiles is like this:
        {
          "profiles" : [ {
            "name" : "MyProfile",
            "description" : "Primum Profile",
            "executors" : [ {
              "configuration" : {
                "client-authns" : [ "client-jwt", "client-secret-jwt", "client-x509" ],
                "client-authns-augment" : null,
                "is-augment" : false
              },
              "executor" : "secure-client-authn-executor"
            } ]
          }, {
            "name" : "UnusedProfile",
            "description" : "Profile with SecureClientAuthEnforceExecutorFactory",
            "executors" : [ {
              "configuration" : {
                "client-authns" : [ "client-jwt", "client-x509" ],
                "client-authns-augment" : null,
                "is-augment" : false
              },
              "executor" : "secure-client-authn-executor"
            } ]
          } ]
        }
        
      • Create client policy linked with "MyProfile"
      • Try to register client with client authentication set to JWTClientSecretAuthenticator.PROVIDER_ID .
        Expected behaviour: Creation of client is allowed as policy is linked with "MyProfile", which allows creation of JWTClientSecretAuthenticator.PROVIDER_ID
        Current behaviour: Creation of client is not allowed. Configuration of "UnusedProfile" is used even if it should not be used at all

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mposolda@redhat.com Marek Posolda
              Reporter:
              mposolda@redhat.com Marek Posolda
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: