Hey guys,<div><br></div><div>after talking about the RFCs and so, I couldn&#39;t stop to read them. ;)</div><div><br></div><div>There I stumbled about the test vectors. They are not working with the aerogear-implementation, because of the Base32 encoding which is used by the google authenticator.</div>

<div>The used secret in the rfc is &quot;1234567890&quot;, which is not valid google, because Base32 uses ABCDEFGHIJKLMNOPQRSTUVWXYZ234567.</div><div><br></div><div>vectors:</div><div><a href="http://tools.ietf.org/html/rfc6238#appendix-B">http://tools.ietf.org/html/rfc6238#appendix-B</a><br clear="all">

<div><br></div><div>Using the &quot;reference implementation&quot;, which is provided in document the generated token is different from aerogear one.</div><div><br></div><div><br></div><div>Is the plan to support the RFC or Google? (or better both? :))</div>

-- <br>Viele Grüße/Best Regards<br><br>Daniel Manzke<br>
</div>