it means the logon tile the user picked is NOT the one the administrator set for them, for example, the user picked to login with a smart card, but the user is set to use a password.
Thanks for the answer
The strange thing is that all users has Password only tokens in their settings,
and users can't choose other than Password only token at the login screen. Still they get The token is not correct one.
somewhere, someone picked a different token for them.
Find the user in EEM and look at their token screen, if it says password, recreate the token for them.
someone might have switched them to something else, then switched back thinking that would be fine - it's not. If you switch away from the Password token, the local token data gets zeroed (for security).
This is interesting... We also just experienced this in the last month. Simon, are you saying this has been an issue before? Just ironic that people are starting to see this over the last month.
We too have seen this only in about the last month.
We have admins who have been logging in for well over two years now and never had this problem until now.
Most cases we can resolve the issue by recreating their password only token.
Sometimes we need to delete the user and re add the user to make the problem go away.
There is a bug somewhere just not sure where it might be.
it's a very specific message - it's not reporting a code issue, it's reporting that the unique 32bit token number being selected is NOT the one currently assigned to the user.
I can't see how it would occur through corruption etc. It would have to be either a connector set to create users with the wrong token, an admin accidentally changing the token through recovery or clicking, or the user simply selecting the wrong tile...
We are also starting to see this. Only password tokens are used and it sporatically is happening on a few. The version we are using is 523.
same answer - one end or the other the token is wrong - either the user is not choosing "password token", or some naughty admin set a different token for them, in the connector, or in EEM.
I have been watching this on our system. Simon's explanation isn't all inclusive and there are many factors that can do this. I had my admin password change, but I tracked it to logging into three different computers that hadn't sync'd since I changed my password over a two week period. After the third one sync'd using my old password, my password in the database changed back to old one. In the forum, there are topics of workstation time setting versus database time. I think if you look at audit logs of workstations and users you can track what happened.