Ok, that one's Ignition, but now you have different 2 clients seeing the exact same a similar issue... maybe it's time to get the Server vendor involved.
Ignition gets BadIdentityTokenRejected, not BadIdentityTokenInvalid, though... which might again suggest you just have the wrong username/password.