[
https://issues.jboss.org/browse/WFLY-7586?page=com.atlassian.jira.plugin....
]
Jan Kalina commented on WFLY-7586:
----------------------------------
Reproducible with upstream wildfly-core + elytron-subsystem (rest of wildfly or incubator
versions of wildfly-core not needed).
Wrong output is sent as response to "suggest-capabilities" request - not CLI
problem.
Problem is in CapabilityRegistry (wildfly-core/server) - getDynamicCapabilityNames():
* method is asked for security-realm capability (referencedCapability =
"org.wildfly.security.security-realm")
* method filter two capabilities: "org.wildfly.security.security-realm.ldapName"
and "org.wildfly.security.modifiable-security-realm.ldapName"
* method substring by length of referencedCapability (which cause
"rity-realm.ldapName")
*The problem is, that CapabilityRegistry.getDynamicCapabilityNames() obtains all paths
referring some realms and create matchers from them - later all matching capabilities are
obtained - even through they are not referencedCapability - must be fixed in core.*
Wrong options for auto-completion in realms of Elytron
security-domain in CLI
-----------------------------------------------------------------------------
Key: WFLY-7586
URL:
https://issues.jboss.org/browse/WFLY-7586
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Ondrej Lukas
Assignee: Jan Kalina
Labels: user_experience
Auto-completion for realm in realms of security-domain provides wrong options. In case
when ldap-realm with name ldapName is defined in configuration then also option
{{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this
issue with properties-realm. Take a look at Steps to Reproduce for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)