I’m showing some weird behavior on the Spark 2.5.8 side where some contacts appear as offline and have incorrect JID’s i.e poorschmuck@z-openfire instead of the normal AD/LDAP contacts in the roster showing as valid, i.e SCHMUCK Poor.
Any ideas? LDAP latency? Old roster info on the client side? Please see attached.