Device ID does not match the token. about stoken HOT 7 CLOSED

Issue resolved, had to use the full url as the token and not just numbers.

from stoken.

So your token works with the Android RSA app, but not with stoken or Easy Token?

Uninstalling and wiping all data of com.rsa.securidapp on my phone and then installing it and importing the token again and verifying I am still able to authenticate.

Does this mean the same token string still works even after com.rsa.securidapp has changed the device ID? If so, it may be using a fixed ID hardcoded into the app.

from stoken.

1)The token works with the Android RSA app and I just installed and tested with Easy Token and it works too.

2)That is correct, same token works even after device ID has changed.

from stoken.

Can you try entering device ID: a01c4380-fc01-4df0-b113-7fb98ec74694

Building stoken from git

Can you double-check that any old stoken versions are uninstalled from your system before running the newly compiled binary?

from stoken.

Verified old stoken and libraries were gone and built from git, tried a01c4380-fc01-4df0-b113-7fb98ec74694 as the device ID and got:
Device ID does not match the token.

from stoken.

Ah, right, bound devids are handled differently between feature phones (numeric string) and smart phones (full URL).

With v3 tokens I could potentially try both options because the hash is pretty foolproof, but on v2 tokens, guessing will occasionally result in undetectable bad decrypts.

from stoken.

Where do I get the full url?

from stoken.