CLOUD and Support should be aware of this change at it promotes otherwise "soft" error during LDAP name mapping into "hard" errors.
This change is important as a transient network error could lead to an erroneous name mapping if an early, higher priority rule fails for non-schema related reasons, but a later fallback rule does not.
If this causes customer issues, TSEs should be prepared to use setParameter `ldapAbortOnNameMappingFailure=false` to disable the new abort on error behavior. This setting should NOT be advertised in DOCS as using it has the potential to weaken authorization security as noted above.