Previously, if you made an update on an LDAP server, the `LegacyLDAPSecuritySettingPlugin` security settings plugin configured on the broker might not immediately detect the change. For example, if you added a new user to an existing group on the LDAP server, the plugin did not immediately authorize the new user with the same broker permissions as existing users in the same group. Instead, for a change such as this to take effect, you needed to restart the broker. This issue is now resolved.

Create a server in Apache DS Studio Create partition dc=cloud,dc=smals,dc=be Start the server and import the [^ldap-export.ldif] under the partition Create a broker using the [^broker.xml] and [^login.config] Test user3 access sh bin/artemis queue stat --queueName project1.testldap --password user3 --user user3 Import [^team4.ldif] under the partition, with Update existing entries checked Test user4 access that will fail with the message AMQ229213: User: user4 does not have permission='CREATE_NON_DURABLE_QUEUE' sh bin/artemis queue stat --queueName project1.testldap --password user4 --user user4 restart the broker Test user4 access that now will works.