[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ]
Martin Choma updated WFWIP-315:
-------------------------------
Attachment: standalone-openshift.cd19.xml
standalone-openshift.xp.xml
> XP OpenShift image http management interface secured with no user by default
> ----------------------------------------------------------------------------
>
> Key: WFWIP-315
> URL: https://issues.redhat.com/browse/WFWIP-315
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-openshift.cd19.xml, standalone-openshift.xp.xml
>
>
> In one test with XP image [1] I am experiencing problem of failing rediness probe.
> {code}
> sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe
> DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe'])
> INFO:__main__:Loading probe: probe.eap.dmr.EapProbe
> DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe
> DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY]
> INFO:__main__:Running probes
> INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe]
> INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe
> INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest]
> INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management
> DEBUG:probe.eap.dmr.EapProbe:Probe request = {
> "operation": "composite",
> "json.pretty": 1,
> "steps": [
> {
> "operation": "read-attribute",
> "name": "server-state"
> },
> {
> "operation": "read-boot-errors",
> "address": {
> "core-service": "management"
> }
> },
> {
> "operation": "read-attribute",
> "name": "status",
> "address": {
> "deployment": "*"
> }
> }
> ],
> "address": []
> }
> INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost
> DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188
> DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]>
> ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request
> Traceback (most recent call last):
> File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute
> results = self.sendRequest(request)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest
> self.failUnusableResponse(response, request, url)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse
> unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"]
> KeyError: 'result'
> INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE]
> DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'"
> {code}
> Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron.
> When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties
> In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication" console-enabled="false">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19)
> [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ]
Martin Choma edited comment on WFWIP-315 at 4/27/20 3:11 AM:
-------------------------------------------------------------
CC: [~luck3y] [~jdenise]
was (Author: mchoma):
CC: [~luck3y][~jdenise]
> XP OpenShift image http management interface secured with no user by default
> ----------------------------------------------------------------------------
>
> Key: WFWIP-315
> URL: https://issues.redhat.com/browse/WFWIP-315
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
>
> In one test with XP image [1] I am experiencing problem of failing rediness probe.
> {code}
> sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe
> DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe'])
> INFO:__main__:Loading probe: probe.eap.dmr.EapProbe
> DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe
> DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY]
> INFO:__main__:Running probes
> INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe]
> INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe
> INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest]
> INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management
> DEBUG:probe.eap.dmr.EapProbe:Probe request = {
> "operation": "composite",
> "json.pretty": 1,
> "steps": [
> {
> "operation": "read-attribute",
> "name": "server-state"
> },
> {
> "operation": "read-boot-errors",
> "address": {
> "core-service": "management"
> }
> },
> {
> "operation": "read-attribute",
> "name": "status",
> "address": {
> "deployment": "*"
> }
> }
> ],
> "address": []
> }
> INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost
> DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188
> DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]>
> ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request
> Traceback (most recent call last):
> File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute
> results = self.sendRequest(request)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest
> self.failUnusableResponse(response, request, url)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse
> unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"]
> KeyError: 'result'
> INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE]
> DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'"
> {code}
> Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron.
> When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties
> In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication" console-enabled="false">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19)
> [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ]
Martin Choma commented on WFWIP-315:
------------------------------------
CC: [~luck3y][~jdenise]
> XP OpenShift image http management interface secured with no user by default
> ----------------------------------------------------------------------------
>
> Key: WFWIP-315
> URL: https://issues.redhat.com/browse/WFWIP-315
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
>
> In one test with XP image [1] I am experiencing problem of failing rediness probe.
> {code}
> sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe
> DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe'])
> INFO:__main__:Loading probe: probe.eap.dmr.EapProbe
> DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe
> DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY]
> INFO:__main__:Running probes
> INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe]
> INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe
> INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest]
> INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management
> DEBUG:probe.eap.dmr.EapProbe:Probe request = {
> "operation": "composite",
> "json.pretty": 1,
> "steps": [
> {
> "operation": "read-attribute",
> "name": "server-state"
> },
> {
> "operation": "read-boot-errors",
> "address": {
> "core-service": "management"
> }
> },
> {
> "operation": "read-attribute",
> "name": "status",
> "address": {
> "deployment": "*"
> }
> }
> ],
> "address": []
> }
> INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost
> DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188
> DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]>
> ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request
> Traceback (most recent call last):
> File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute
> results = self.sendRequest(request)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest
> self.failUnusableResponse(response, request, url)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse
> unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"]
> KeyError: 'result'
> INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE]
> DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'"
> {code}
> Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron.
> When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties
> In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication" console-enabled="false">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19)
> [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ]
Martin Choma updated WFWIP-315:
-------------------------------
Comment: was deleted
(was: Setting target release 7.3.1.GA, because I don't see XP version yet. )
> XP OpenShift image http management interface secured with no user by default
> ----------------------------------------------------------------------------
>
> Key: WFWIP-315
> URL: https://issues.redhat.com/browse/WFWIP-315
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
>
> In one test with XP image [1] I am experiencing problem of failing rediness probe.
> {code}
> sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe
> DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe'])
> INFO:__main__:Loading probe: probe.eap.dmr.EapProbe
> DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe
> DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY]
> INFO:__main__:Running probes
> INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe]
> INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe
> INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest]
> INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management
> DEBUG:probe.eap.dmr.EapProbe:Probe request = {
> "operation": "composite",
> "json.pretty": 1,
> "steps": [
> {
> "operation": "read-attribute",
> "name": "server-state"
> },
> {
> "operation": "read-boot-errors",
> "address": {
> "core-service": "management"
> }
> },
> {
> "operation": "read-attribute",
> "name": "status",
> "address": {
> "deployment": "*"
> }
> }
> ],
> "address": []
> }
> INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost
> DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188
> DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]>
> ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request
> Traceback (most recent call last):
> File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute
> results = self.sendRequest(request)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest
> self.failUnusableResponse(response, request, url)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse
> unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"]
> KeyError: 'result'
> INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE]
> DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'"
> {code}
> Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron.
> When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties
> In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication" console-enabled="false">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19)
> [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ]
Martin Choma moved JBEAP-19357 to WFWIP-315:
--------------------------------------------
Project: WildFly WIP (was: JBoss Enterprise Application Platform)
Key: WFWIP-315 (was: JBEAP-19357)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: OpenShift
(was: OpenShift)
Target Release: (was: 7.3.1.GA)
Affects Version/s: (was: 7.3.1.CR1)
> XP OpenShift image http management interface secured with no user by default
> ----------------------------------------------------------------------------
>
> Key: WFWIP-315
> URL: https://issues.redhat.com/browse/WFWIP-315
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
>
> In one test with XP image [1] I am experiencing problem of failing rediness probe.
> {code}
> sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe
> DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe'])
> INFO:__main__:Loading probe: probe.eap.dmr.EapProbe
> DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe
> DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=***
> INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY]
> INFO:__main__:Running probes
> INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe]
> INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe
> INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest]
> INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management
> DEBUG:probe.eap.dmr.EapProbe:Probe request = {
> "operation": "composite",
> "json.pretty": 1,
> "steps": [
> {
> "operation": "read-attribute",
> "name": "server-state"
> },
> {
> "operation": "read-boot-errors",
> "address": {
> "core-service": "management"
> }
> },
> {
> "operation": "read-attribute",
> "name": "status",
> "address": {
> "deployment": "*"
> }
> }
> ],
> "address": []
> }
> INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost
> DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188
> DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]>
> ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request
> Traceback (most recent call last):
> File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute
> results = self.sendRequest(request)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest
> self.failUnusableResponse(response, request, url)
> File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse
> unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"]
> KeyError: 'result'
> INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE]
> DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'"
> {code}
> Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron.
> When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties
> In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication" console-enabled="false">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19)
> [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.
by Alexander Golovko (Jira)
[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ]
Alexander Golovko updated WFLY-13405:
-------------------------------------
Description:
Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument.
was:
Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); is error. It raises MissingFormatArgumentException exception since new Object[0] is empty array and it not compatible with %s in format argument.
> Update CommonDeploymentService in release.
> ------------------------------------------
>
> Key: WFLY-13405
> URL: https://issues.redhat.com/browse/WFLY-13405
> Project: WildFly
> Issue Type: Bug
> Reporter: Alexander Golovko
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: debug.log
>
>
> Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.
by Alexander Golovko (Jira)
[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ]
Alexander Golovko commented on WFLY-13405:
------------------------------------------
Just check
wildfly-19.0.0.Final\modules\system\layers\base\org\jboss\as\connector\main\wildfly-connector-19.0.0.Final.jar\org\jboss\as\connector\subsystems\datasources\CommonDeploymentService.class
> Update CommonDeploymentService in release.
> ------------------------------------------
>
> Key: WFLY-13405
> URL: https://issues.redhat.com/browse/WFLY-13405
> Project: WildFly
> Issue Type: Bug
> Reporter: Alexander Golovko
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: debug.log
>
>
> Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); is error. It raises MissingFormatArgumentException exception since new Object[0] is empty array and it not compatible with %s in format argument.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years