]
Darran Lofthouse commented on WFCORE-1038:
------------------------------------------
It appears this is caused by the following commit: -
We probably need CLI side validation to take into account if one of the alternatives has
been set.
Unable to configure LDAP based authentication within a SecurityRealm
using the CLI
----------------------------------------------------------------------------------
Key: WFCORE-1038
URL:
https://issues.jboss.org/browse/WFCORE-1038
Project: WildFly Core
Issue Type: Bug
Components: CLI, Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 2.0.0.CR7
The first and last errors reported here are coming from the CLI: -
{noformat}
[standalone@localhost:9990 /]
./core-service=management/security-realm=ManagementRealm/authentication=ldap:add(username-attribute=uid,
base-dn=cn=base, connection=LdapSsl)
The following parameters 'advanced-filter' are required
[standalone@localhost:9990 /]
./core-service=management/security-realm=ManagementRealm/authentication=ldap:add(username-attribute=uid,
advanced-filter=(uid={0}), base-dn=cn=base, connection=LdapSsl)
{
"outcome" => "failed",
"failure-description" => "WFLYDM0035: Only one of
'username-attribute' or 'advanced-filter' is required.",
"rolled-back" => true,
"response-headers" => {"process-state" =>
"reload-required"}
}
[standalone@localhost:9990 /]
./core-service=management/security-realm=ManagementRealm/authentication=ldap:add(advanced-filter=(uid={0}),
base-dn=cn=base, connection=LdapSsl)
The following parameters 'username-attribute' are required
{noformat}