Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Critical
Fix Version/s: 7.2.10.GA
Affects Version/s: 7.2.9.CR1
Component/s: Management, Security
Labels:
- regression

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Text:

Hide
Resolved in EAP 7.3.3 - ~~JBEAP-19808~~

Show
Resolved in EAP 7.3.3 - JBEAP-19808
Target Release:

7.2.z.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/935
Steps to Reproduce:

Hide

Follow the readme in the attached [^reproducer.zip]

Show
Follow the readme in the attached [^reproducer.zip]

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

We have SASL enabled for the management interface and the client is configured to use credentials from a store via wildfly-config.xml.

But running a command like

jboss-cli.sh -Dwildfly.config.url=wildfly-config.xml --connect --commands=":read-attribute(name=server-state)"

still results in the client asking for credentials.

This is a regression against EAP 7.3.1.

Looks like this is caused by ~~JBEAP-19531~~

clones

JBEAP-19808 [QE](7.3.z) WFCORE-5028 - Client with credentials defined in wildfly-config still prompts the user to provide them

Verified

is caused by

JBEAP-19532 [GSS](7.2.z) WFCORE-4976 - Where ModelControllerClient is initialised in process with CBH AuthenticationConfiguration takes priority.

Closed

Assignee:: Ilia Vassilev

Reporter:: Ricardo Martin Camarero

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2020/07/02 9:04 AM

Updated:: 2021/10/24 6:15 AM

Resolved:: 2020/12/02 10:42 AM