运行Wildfly-17单机版失败，原因是配置异常不合理

Question

为LDAP身份验证配置Wildfly-17失败，并出现异常，告知身份验证下不允许使用属性标记，这是不合理的，因为异常说明身份验证下唯一允许的标记为：

|                 jaas        local       truststore  
|                 kerberos    plug-in     users       
|                 ldap        ***properties***

我尝试刷新服务器，然后重新启动它，但仍然得到相同的异常，下面是我的standalone-full.xml配置文件：

<security-realm name="ManagementRealm">
                <authentication>
                    <local default-user="$local" skip-group-loading="true"/>
                    <ldap connection="EC2" base-dn="CN=Users,DC=mydc1,DC=mydc2,DC=org">
                        <username-filter attribute="sAMAccountName" />
                    </ldap>
                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
                </authentication>
                <authorization map-groups-to-roles="false">
                    <properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/>
                </authorization>
            </security-realm>

以下是异常消息：

OPVDX001: Validation error in standalone-full.xml ------------------------------
|
|  50:         <username-filter attribute="sAMAccountName" />
|  51:     </ldap>
|  52:     <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
|          ^^^^ 'properties' isn't an allowed element here
|               
|               Elements allowed here are: 
|                 jaas        local       truststore  
|                 kerberos    plug-in     users       
|                 ldap        properties  
|
|  53: </authentication>
|  54: <authorization map-groups-to-roles="false">
|  55:     <properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/>
|
| 'properties' is allowed in elements: 
| - server > management > security-realms > security-realm > authentication
| - server > management > security-realms > security-realm > authentication > plug-in
| - server > management > security-realms > security-realm > authorization
| - server > management > security-realms > security-realm > authorization > plug-in
| - server > management > outbound-connections > ldap

Answer 1

将属性元素放在第一位可以解决问题