none
Does the Microsoft Authenticator App support the digits, algorithm and period fields? RRS feed

  • Question

  • When scanning an TOTP QR Code (otpauth://totp/...) the Microsoft Authenticator App appears to ignore the digits, algorithm and period fields.

    Does anyone know whether these fields are supported? 

    I've tried to use a 8 digit code using the SHA512 algorithm, but the app will default to a 6 digit code with SHA1.

    Any hints/tips would be welcome!

    Monday, March 27, 2017 8:08 PM

All replies

  • Hi Tino,

    Microsoft authenticator app default hash method is SHA-1, default token length is 6.

    As far as I know, Microsoft Authenticator App does not support to use an 8 digit code and use SHA512.

    Best regards,

    Jason


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 28, 2017 10:05 AM
  • This is correct; the DEFAULT behavior for the app is to use HmacSHA1 for hashing and a 6-digit code. The 'algorithm' and 'digit' fields in the otpauth QR Code appears to be ignored.

    Yet, when you use the Microsoft Authenticator App for your Microsoft Account (MSA), you will se that an 8-digit code is possible.

    Tuesday, April 11, 2017 8:58 AM
  • Hi Tino,

    Sorry, I did not describe it clearly in my first replay.

    You are right, Microsoft Authenticator App use 8-digits code for Microsoft Account, and the settings of digit length controlled by the Microsoft Account server side.

    When we add Azure AD user account to Microsoft Authenticator App, App will use 6-digits for Azure AD user, we can’t set up digit length in Microsoft Authenticator App. I also tried to search the settings in Azure AD, but I didn’t find any attributes about digit length.

    In my opinion, we can’t modify the digit length.

    Best regards,

    Jason


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 13, 2017 7:50 AM