Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6681

Is impossible remove whole Elytron subsystem when Elytron resource depends on another Elytron resource.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR9
    • 7.1.0.DR7
    • Security
    • None
    • Hide
      • firefly.keystore which is attached copy to eap_home/standalone/data.
      • run EAP server
        ./bin/standalone.sh
      • run CLI
        ./bin/jboss-cli.sh -c
        if applicaple add Elytron extension and Elytron subsystem and reload server
        /extension=org.wildfly.extension.elytron:add()
        /subsystem=elytron:add()
        reload
      • /subsystem=elytron/credential-store=credStore:add(uri="cr-store://test/scratchSC.jceks?create.storage=true;store.password=pass123")
/subsystem=elytron/credential-store=credStore/alias=ff:add(secret-value=Elytron)
/subsystem=elytron/key-store=firefly:add(path=firefly.keystore,relative-to=jboss.server.data.dir,type=JKS,credential-reference={store=credStore,alias=ff})
/subsystem=elytron:remove()

        Alternative faster way to reproduce: use attached standalone-removing.xml and run: 

        /subsystem=elytron:remove()

        (keystore file does not need to exist to reproduce this)

      Show
      firefly.keystore which is attached copy to eap_home/standalone/data. run EAP server ./bin/standalone.sh run CLI ./bin/jboss-cli.sh -c if applicaple add Elytron extension and Elytron subsystem and reload server /extension=org.wildfly.extension.elytron:add() /subsystem=elytron:add() reload /subsystem=elytron/credential-store=credStore:add(uri= "cr-store: //test/scratchSC.jceks?create.storage= true ;store.password=pass123" ) /subsystem=elytron/credential-store=credStore/alias=ff:add(secret-value=Elytron) /subsystem=elytron/key-store=firefly:add(path=firefly.keystore,relative-to=jboss.server.data.dir,type=JKS,credential-reference={store=credStore,alias=ff}) /subsystem=elytron:remove() Alternative faster way to reproduce: use attached standalone-removing.xml and run: /subsystem=elytron:remove() (keystore file does not need to exist to reproduce this)

    Description

      Is impossible remove whole Elytron subsystem by one command when Elytron resource depends on another Elytron resource.

      Scenario:

      • I have KeyStore in Elytron subsystem with CredentialStoreReference set to CredentialStore
      • I want to delete whole Elytron subsystem
      • I execute this CLI command /subsystem=elytron:remove() and get error 
        {
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service org.wildfly.security.credential-store-client.credStore was depended upon by service org.wildfly.security.key-store.firefly",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

      NOTES:

      • When I perform CLI command /subsystem=elytron:remove() again as it passes.
      • When I use for remove {allow-resource-service-restart=true} as /subsystem=elytron:remove(){allow-resource-service-restart=true}

        then result is successful.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7619 Is impossible remove whole Elytron subsystem when Elytron resource depends on another Elytron resource.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-7538 Upgrade Elytron Subsystem to 1.0.0.Alpha15

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              jkalina@redhat.com Jan Kalina (Inactive)
              hsvabek_jira Hynek Švábek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: