From 840a99b253e11554c166ccd7de22b553db627ee3 Mon Sep 17 00:00:00 2001 From: Jiangge Zhang Date: Wed, 3 Jun 2015 23:58:10 +0800 Subject: Move the external link to page bottom. --- docs/hazmat/primitives/twofactor.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/hazmat/primitives/twofactor.rst b/docs/hazmat/primitives/twofactor.rst index e149da02..f49d02f9 100644 --- a/docs/hazmat/primitives/twofactor.rst +++ b/docs/hazmat/primitives/twofactor.rst @@ -193,9 +193,8 @@ Provisioning URI ~~~~~~~~~~~~~~~~ The provisioning URI of HOTP and TOTP is not actual the part of RFC 4226 and -RFC 6238, but a `spec of Google Authenticator `_. It is -widely supported by web sites and mobile applications which are using -Two-Factor authentication. +RFC 6238, but a `spec of Google Authenticator`_. It is widely supported by web +sites and mobile applications which are using Two-Factor authentication. For generating a provisioning URI, you could use the ``get_provisioning_uri`` method of HOTP/TOTP instances. @@ -211,3 +210,5 @@ method of HOTP/TOTP instances. A common usage is encoding the provisioning URI into QR code and guiding users to scan it with Two-Factor authentication applications in their mobile devices. + +.. _`spec of Google Authenticator`: https://github.com/google/google-authenticator/wiki/Key-Uri-Format -- cgit v1.2.3