Answer
Check whether the imported user's Identity field retained the Active Directory domain prefix from the import (e.g. an Identity of ml\richardm instead of just richardm). Removing that domain-prefix portion from the Identity value in Solution Manager > Security > Users (leaving just the plain username) resolves this exact 'Invalid Login Details' pattern for LDAP-imported accounts, even when every other setting (active, enabled, password) looks correct.