Forum Discussion

esardinha's avatar
esardinha
Copper Contributor
Jun 05, 2019

Oath hardware token

Hi All, I just received my hardware tokens to set up for a few users in our organization that do not have access to company mobile devices. I have uploaded the .csv files with the required informat...
azure
Security & Compliance
Jeff_Birks's avatar
Jeff_Birks
Copper Contributor
Jul 10, 2024
There are several possible causes, but the most important thing to have correct is the contents of the CSV file that you uploaded. Some time ago I noticed the official Microsoft guide's example included seed data that was hex encoded (for microsoft the data should only be base32 enocded) on one page the example was partially corrected, but I see elsewhere they have an example that is still hex encoded. I would first check that your seed data is Base32 encoded, and that you have a time window that matches the tokens you are uploading (either 30 or 60 seconds).

If you used a programmable token (such as the safeid diamond token), then you may will have selected the time window time yourself when burning the token (so again ensure the time window and seed data match).

I also strongly suggest using a text editor when editing the seed file, and do not use a spreadsheet (as this can corrupt some numeric data in the file).
  • A34504's avatar
    A34504
    Copper Contributor
    Aug 22, 2024
    Hi Jeff.
    I have a similar issue but I am able to upload the file without any error. Then when I try to activate the token, it just says the below error
    Failed to activate the selected OATH token. I tried it for multiple token but it is not working..

    I however was able to activate one token but thereafter I am not able to activate any. The token is from Feitian.
    • franklandwehr's avatar
      franklandwehr
      Copper Contributor
      Sep 05, 2024

      A34504 

      The same here, I activated some OATH in the past, but I'm not able to activate this now. Allready tried 3 different Token.

      "Failed to activate the selected OATH token."

      • PietN's avatar
        PietN
        Copper Contributor
        Sep 11, 2024

        franklandwehr 

        I have got the same problem. The token worked oke for a while, but suddenly not anymore. So removed the tokens and added them again. That went oke. But activation is not possible (anymore).

    • Jeff_Birks's avatar
      Jeff_Birks
      Copper Contributor
      Sep 26, 2024

      Did you remember to add the UPN details column - that may be the issue (also as mentioned earlier, only use a text editor).

       

      If there are still issue it may be due to the age of the token.  When registering the token Microsoft will allow a decent amount of time drift, but there is a limit to how much drift they will accept.

       

      You might find the following wiki guide useful for checking the extent of time drift on a hardware token (should work with any make);

      https://wiki.deepnetsecurity.com/display/SafeID/Determining+the+extent+of+time+drift+on+Pre-Programmed+TOTP+Tokens 

    • Jeff_Birks's avatar
      Jeff_Birks
      Copper Contributor
      Oct 09, 2024
      It could be that you didn't include the UPN details in the CSV file, but a real possibility is that the file was not edited with a text editor. By default the CSV files will load into a spreadsheet but you should avoid this happening as it is likely to corrupt the file prior to upload (the number format for the serial numbers for example).

Resources