j256/two-factor-auth

Issues

• Google's QR API is dead

  #34 opened 7 months ago by echometerain
  11

• "Key not recognized" in Google Authenticator app

  #32 opened 2 years ago by Testehan
  3

• code is not validating

  #30 opened 2 years ago by priyankatech2513
  1

• Auth keys are invalid after server restart

  #31 opened 2 years ago by OrganicCat
  1

• generateCurrentNumberString cannot match with the authenticator's code

  #22 opened 4 years ago by Ye37Xin
  3

• google authenticator 不是有效的身份验证令牌

  #9 opened 4 years ago by ValueInvest
  8

• Compatibility with hardware devices instead of auth apps?

  #11 opened 4 years ago by ovizii
  1

• Use with TOTP systems that generate Hex secrets

  #20 opened 4 years ago by craigmit
  0

• windowMillis setting is not correct

  #10 opened 4 years ago by bino7
  3

• Custom QR Image Dimensions

  #12 opened 4 years ago by alvin-reyes
  1

• does this repo support MS authenticator?

  #18 opened 4 years ago by rayeaster
  2

• generateCurrentNumber() returns long but validateCurrentNumber() accepts an int

  #13 opened 5 years ago by seantcanavan
  2

• qrImageUrl invalid for google authenticator

  #16 opened 6 years ago by RealZimboGuy
  4

• Invalid base-32 character: _

  #7 opened 7 years ago by GoldenScrew
  3

• Use generateBase32Secret()

  #8 opened 7 years ago by GoldenScrew
  2

• Separate otpauth portion of QR Url

  #6 opened 8 years ago by jball
  3

• Problem with invalid base-32 secret causing ArrayIndexOutOfBoundsException

  #5 opened 8 years ago by wying111
  5

• License

  #4 opened 9 years ago by karatemaccie
  1

• License?

  #1 opened 9 years ago by atoulme
  2