[JBoss JIRA] (WFLY-7781) Regression in EAP 7.1.0.DR9: username-load attribute of legacy LDAP Realm stop to work
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7781:
----------------------------------
Summary: Regression in EAP 7.1.0.DR9: username-load attribute of legacy LDAP Realm stop to work
Key: WFLY-7781
URL: https://issues.jboss.org/browse/WFLY-7781
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
{{username-load}} attribute of legacy LDAP Realm stop to work in EAP 7.1.0.DR9. This attribute is used for assigning username from some LDAP entry attribute. In current behavior in EAP 7.1.0.DR9 username passed in credential is used as username even if username-load attribute is configured.
Due to regression we request blocker. Taking EAP 7.0.x configuration and put it into EAP 7.1.x will causes that username-load feature stop to work.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2107) CLI, Test, clean output once started in interactive mode
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2107:
--------------------------------------------
Summary: CLI, Test, clean output once started in interactive mode
Key: WFCORE-2107
URL: https://issues.jboss.org/browse/WFCORE-2107
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Jean-Francois Denise
On some platforms, the tests that make use of executeInteractive (e.g.: CLIConfigTestCase), fail randomly with the wrong output being retrieved from the remote process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JGRP-2144) FD_HOST doesn't print stack trace
by Osamu Nagano (JIRA)
Osamu Nagano created JGRP-2144:
----------------------------------
Summary: FD_HOST doesn't print stack trace
Key: JGRP-2144
URL: https://issues.jboss.org/browse/JGRP-2144
Project: JGroups
Issue Type: Bug
Reporter: Osamu Nagano
Assignee: Bela Ban
Priority: Minor
Something happened in {{FD_HOST}} but a stack trace is omitted, which could have a clue to the root cause.
{code}
2016-11-02 15:55:49,738 SEVERE [org.jgroups.protocols.FD_HOST] (Timer-2,ekdgp331-53459) node331-53459: ping command failed: java.lang.NullPointerException
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months