Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5908

Credential store resource 'state' attribute fails with SecretKeyCredentialStoreDefinition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 19.0.0.Beta9
    • Security
    • None

      A PR in full WF is seeing failures in org.jboss.as.test.integration.management.api.ClientCompatibilityUnitTestCase's recursive read of the management model, including runtime-only attributes. Problem occurs when reading a secret-key-credential-store resource.

      https://ci.wildfly.org/viewLog.html?buildId=304633&tab=buildResultsDiv&buildTypeId=WF_PullRequest_LinuxSmJdk11#testNameId808114965116086878

      https://github.com/wildfly/wildfly/pull/15185

      The failure:

      10:29:38,930 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
          ("subsystem" => "elytron"),
          ("secret-key-credential-store" => "MDBWithVaultedPropertiesTestCase")
      ]): java.lang.IllegalArgumentException: WFLYELY00003: The operation did not contain an address with a value for 'credential-store'.
      	at org.wildfly.extension.elytron@19.0.0.Beta9//org.wildfly.extension.elytron.ServiceUtil.serviceName(ServiceUtil.java:80)
      	at org.wildfly.extension.elytron@19.0.0.Beta9//org.wildfly.extension.elytron.AbstractCredentialStoreResourceDefinition$1.executeRuntimeStep(AbstractCredentialStoreResourceDefinition.java:129)
      	at org.jboss.as.controller@19.0.0.Beta9//org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:59) 
      

      The problem is AbstractCredentialStoreResourceDefinition.CREDENTIAL_STORE_UTIL is configured to only accept address with key 'credential-store', so it will reject 'secret-key-credential-store'.

      Why this only appears on that PR is unknown; the fact the resource being read indicates some previous test did not adequately clean up state. But that's just fortuitous as it revealed this bug.

              fjuma1@redhat.com Farah Juma
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: