Token expired when scanning a Totp generated Uri on "Authy Authenticator App"
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 179
- PR merge metrics
- No merged PRs in 30d
Description
Google, Microsoft, Duo can successfully scan TOTP QrCodes and work flawlessly with this library. However Authy does not seem to recognize the token format at all, when it clearly states that this type of QR Code should be supported? Can you verify this ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the generated TOTP URI with Authy and compare it with the same URI in Google, Microsoft, and Duo Authenticator; inspect the library's URI-generation entry point. Done means identifying whether the URI format is incompatible with Authy and documenting or fixing the behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100