After attempting to use this library, I found that generated OTPauth URLs showed as "Invalid token" when scanned into FreeOTP. Removing this extra colon allowed FreeOTP to understand the URL, and the generated codes then worked on Battle.NET.
I don't fully understand the OTPauth URL format, but this worked for me, so I figured I'd send in a PR.
jleclanche
commented
7 years ago
Hello,
After attempting to use this library, I found that generated OTPauth URLs showed as "Invalid token" when scanned into FreeOTP. Removing this extra colon allowed FreeOTP to understand the URL, and the generated codes then worked on Battle.NET.
I don't fully understand the OTPauth URL format, but this worked for me, so I figured I'd send in a PR.