[JBoss JIRA] (WFLY-8923) Modifying security in installer fails for domain configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8923?page=com.atlassian.jira.plugin.... ]
Brian Stansberry edited comment on WFLY-8923 at 6/12/17 10:57 AM:
------------------------------------------------------------------
[~simkam] [~jbliznak] The suspicion this is related to WFCORE-2849 is correct. The real problem is WFCORE-2945, but WFCORE-2849 has revealed it. Which I suppose is good and bad. :)
I believe (but haven't confirmed) that in previous releases executing those ops would have resulted in the HC being put in reload-required state, which was also incorrect.
was (Author: brian.stansberry):
[~simkam] [~jbliznak] The suspicion this is related to WFCORE-2849 is correct. The real problem is WFCORE-2945, but WFCORE-2849 has revealed it. Which I suppose is good and bad. :)
I believe (but haven't confirmed) that in previous releases executing those ops or something similar like the two profile ops in a batch against a non-embedded server, would have resulted in the HC being put in reload-required state, which was also incorrect.
> Modifying security in installer fails for domain configuration
> --------------------------------------------------------------
>
> Key: WFLY-8923
> URL: https://issues.jboss.org/browse/WFLY-8923
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Blizňák
> Assignee: Ken Wills
> Priority: Critical
>
> With ER1 user is unable to configure security modules or JSSE via installer. Doing so result in failed installation.
> The probable cause is change made by WFCORE-2849.
> Eg.these CLI commands (genenerated by installer) have different outcomes in DR19 and ER1:
> {code:java}
> $ bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain:add()
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain/authentication=classic:add(login-modules=[{"code"=>"Client","flag"=>"Required","module-options"=>[("testName"=>"testValue"),]}])
> {code}
> with failure in ER1:
> {code:java}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type EMBEDDED_HOST_CONTROLLER"},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8768) mod_cluster excluded-contexts doesn't exclude slash prefixed /contexts; should perform normalization
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8768?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8768:
---------------------------------
Priority: Major (was: Minor)
> mod_cluster excluded-contexts doesn't exclude slash prefixed /contexts; should perform normalization
> ----------------------------------------------------------------------------------------------------
>
> Key: WFLY-8768
> URL: https://issues.jboss.org/browse/WFLY-8768
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Test instructions:
> {noformat}
> [rhusar@syrah wildfly-11.0.0.Beta1-SNAPSHOT]$ ./bin/jboss-cli.sh -c
> [standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=excluded-contexts,value="default-host:/clusterbench"
> {"outcome" => "success"}
> [standalone@localhost:9990 /] :reload
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=modcluster/:read-proxies-info
> {
> "outcome" => "success",
> "result" => [
> "localhost:9090",
> "Node: [1],Name: node1,Balancer: mycluster,LBGroup: ,Host: 127.0.0.1,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10,Ping: 10,Smax: 26,Ttl: 60,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 73
> Vhost: [1:1:1], Alias: localhost
> Vhost: [1:1:2], Alias: default-host
> Context: [1:1:1], Context: /wildfly-services, Status: ENABLED
> Context: [1:1:2], Context: /clusterbench-passivating, Status: ENABLED
> Context: [1:1:3], Context: /tmp, Status: ENABLED
> Context: [1:1:4], Context: /, Status: ENABLED
> Context: [1:1:5], Context: /clusterbench, Status: ENABLED
> "
> ]
> }
> [standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=excluded-contexts,value="default-host:clusterbench"
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 /] :reload
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=modcluster/:read-proxies-info
> {
> "outcome" => "success",
> "result" => [
> "localhost:9090",
> "Node: [1],Name: node1,Balancer: mycluster,LBGroup: ,Host: 127.0.0.1,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10,Ping: 10,Smax: 26,Ttl: 60,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 69
> Vhost: [1:1:1], Alias: localhost
> Vhost: [1:1:2], Alias: default-host
> Context: [1:1:2], Context: /tmp, Status: ENABLED
> Context: [1:1:3], Context: /clusterbench-passivating, Status: ENABLED
> Context: [1:1:4], Context: /wildfly-services, Status: ENABLED
> Context: [1:1:5], Context: /, Status: ENABLED
> "
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8923) Modifying security in installer fails for domain configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8923?page=com.atlassian.jira.plugin.... ]
Brian Stansberry edited comment on WFLY-8923 at 6/12/17 10:50 AM:
------------------------------------------------------------------
[~simkam] [~jbliznak] The suspicion this is related to WFCORE-2849 is correct. The real problem is WFCORE-2945, but WFCORE-2849 has revealed it. Which I suppose is good and bad. :)
I believe (but haven't confirmed) that in previous releases executing those ops or something similar like the two profile ops in a batch against a non-embedded server, would have resulted in the HC being put in reload-required state, which was also incorrect.
was (Author: brian.stansberry):
[~simkam][~jbliznak] The suspicion this is related to WFCORE-2849 is correct. The real problem is WFCORE-2945, but WFCORE-2849 has revealed it. Which I suppose is good and bad. :)
I believe (but haven't confirmed) that in previous releases executing those ops or something similar like the two profile ops in a batch against a non-embedded server, would have resulted in the HC being put in reload-required state, which was also incorrect.
> Modifying security in installer fails for domain configuration
> --------------------------------------------------------------
>
> Key: WFLY-8923
> URL: https://issues.jboss.org/browse/WFLY-8923
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Blizňák
> Assignee: Brian Stansberry
> Priority: Critical
>
> With ER1 user is unable to configure security modules or JSSE via installer. Doing so result in failed installation.
> The probable cause is change made by WFCORE-2849.
> Eg.these CLI commands (genenerated by installer) have different outcomes in DR19 and ER1:
> {code:java}
> $ bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain:add()
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain/authentication=classic:add(login-modules=[{"code"=>"Client","flag"=>"Required","module-options"=>[("testName"=>"testValue"),]}])
> {code}
> with failure in ER1:
> {code:java}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type EMBEDDED_HOST_CONTROLLER"},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8923) Modifying security in installer fails for domain configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8923?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-8923:
--------------------------------------
Assignee: Ken Wills (was: Brian Stansberry)
> Modifying security in installer fails for domain configuration
> --------------------------------------------------------------
>
> Key: WFLY-8923
> URL: https://issues.jboss.org/browse/WFLY-8923
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Blizňák
> Assignee: Ken Wills
> Priority: Critical
>
> With ER1 user is unable to configure security modules or JSSE via installer. Doing so result in failed installation.
> The probable cause is change made by WFCORE-2849.
> Eg.these CLI commands (genenerated by installer) have different outcomes in DR19 and ER1:
> {code:java}
> $ bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain:add()
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain/authentication=classic:add(login-modules=[{"code"=>"Client","flag"=>"Required","module-options"=>[("testName"=>"testValue"),]}])
> {code}
> with failure in ER1:
> {code:java}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type EMBEDDED_HOST_CONTROLLER"},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8923) Modifying security in installer fails for domain configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8923?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-8923:
----------------------------------------
[~simkam][~jbliznak] The suspicion this is related to WFCORE-2849 is correct. The real problem is WFCORE-2945, but WFCORE-2849 has revealed it. Which I suppose is good and bad. :)
I believe (but haven't confirmed) that in previous releases executing those ops or something similar like the two profile ops in a batch against a non-embedded server, would have resulted in the HC being put in reload-required state, which was also incorrect.
> Modifying security in installer fails for domain configuration
> --------------------------------------------------------------
>
> Key: WFLY-8923
> URL: https://issues.jboss.org/browse/WFLY-8923
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Blizňák
> Assignee: Brian Stansberry
> Priority: Critical
>
> With ER1 user is unable to configure security modules or JSSE via installer. Doing so result in failed installation.
> The probable cause is change made by WFCORE-2849.
> Eg.these CLI commands (genenerated by installer) have different outcomes in DR19 and ER1:
> {code:java}
> $ bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain:add()
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain/authentication=classic:add(login-modules=[{"code"=>"Client","flag"=>"Required","module-options"=>[("testName"=>"testValue"),]}])
> {code}
> with failure in ER1:
> {code:java}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type EMBEDDED_HOST_CONTROLLER"},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-2945) Code is using ProcessType.HOST_CONTROLLER to identify an HC, ignoring EMBEDDED_HOST_CONTROLLER
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2945:
----------------------------------------
Summary: Code is using ProcessType.HOST_CONTROLLER to identify an HC, ignoring EMBEDDED_HOST_CONTROLLER
Key: WFCORE-2945
URL: https://issues.jboss.org/browse/WFCORE-2945
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Ken Wills
RestartParentResourceHandlerBase.requiresRuntime is not accounting for ProcessType.EMBEDDED_HOST_CONTROLLER in its logic, assuming that ProcessType.HOST_CONTROLLER is the only enum value for an HC. This is wrong and is the cause of WFLY-8923.
There may be other similar problems in the code. All uses of ProcessType.HOST_CONTROLLER should be inspected. Probably a ProcessType.isHostController() method should be added (I believe just returning !isServer()) to help guide coders to use the API of ProcessType and not rely on the enum values.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8923) Modifying security in installer fails for domain configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8923?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved JBEAP-11494 to WFLY-8923:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8923 (was: JBEAP-11494)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
Security
(was: Domain Management)
(was: Installer)
(was: Security)
Affects Version/s: (was: 7.1.0.ER1)
Affects Testing: (was: Regression)
> Modifying security in installer fails for domain configuration
> --------------------------------------------------------------
>
> Key: WFLY-8923
> URL: https://issues.jboss.org/browse/WFLY-8923
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Blizňák
> Assignee: Brian Stansberry
> Priority: Critical
>
> With ER1 user is unable to configure security modules or JSSE via installer. Doing so result in failed installation.
> The probable cause is change made by WFCORE-2849.
> Eg.these CLI commands (genenerated by installer) have different outcomes in DR19 and ER1:
> {code:java}
> $ bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain:add()
> [domain@embedded /] /profile=default/subsystem=security/security-domain=mySecurityDomain/authentication=classic:add(login-modules=[{"code"=>"Client","flag"=>"Required","module-options"=>[("testName"=>"testValue"),]}])
> {code}
> with failure in ER1:
> {code:java}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type EMBEDDED_HOST_CONTROLLER"},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months