refactor(mfa): Add totp_url to headless mfa activate response data

[mecampbellsoup]

Description

Adds totp_url to allauth.headless.mfa.response.TOTPNotFoundResponse. The rationale is so that we get a ready-to-render TOTP URI for our frontend and I don't have to re-implement any of the allauth.mfa.views.ActivateTOTPView.get_context_data logic in my application or elsewhere/some other way.

Submitting Pull Requests

General

• Make sure you use semantic commit messages.
  Examples: "fix(google): Fixed foobar bug", "feat(accounts): Added foobar feature".
• All Python code must formatted using Black, and clean from pep8 and isort issues.
• JavaScript code should adhere to StandardJS.
• If your changes are significant, please update ChangeLog.rst.
• If your change is substantial, feel free to add yourself to AUTHORS.

[coveralls]

coverage: 95.708%. remained the same
when pulling 4ee8a11 on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into f6577fa on pennersr:main.

[mecampbellsoup]

@pennersr BTW, I noticed that in headless mode, enabling MFA does not explicitly check the user has authenticated recently. Is that done intentionally? Is the idea that headless allauth applications should enforce that via a separate API call, i.e. to headless:browser:mfa:reauthenticate?

[pennersr]

When activating TOTP, headless invokes flows.totp.activate_totp(), which has raise_if_reauthentication_required(request). Deleting TOTP, viewing and regenerating recovery codes is handled similarly. Doesn't that cover this?

[mecampbellsoup]

Hmmm I will play around and confirm!

[coveralls]

coverage: 95.709% (+0.001%) from 95.708%
when pulling 46f80de on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into f6577fa on pennersr:main.

[mecampbellsoup]

@pennersr closed via 18c7ca4 right?

[coveralls]

coverage: 95.746% (+0.001%) from 95.745%
when pulling b55497d on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into d17010b on pennersr:main.

[coveralls]

coverage: 95.746% (+0.001%) from 95.745%
when pulling c603c19 on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into d17010b on pennersr:main.

[mecampbellsoup]

@pennersr this one ready to go now I think! 🙏

[coveralls]

coverage: 95.746% (+0.001%) from 95.745%
when pulling c005a69 on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into d17010b on pennersr:main.

[pennersr]

This description seems off -- it is not a QR code right, nor is it URL encoded. It's just a URL/URI , from which the QR code could be generated.

[mecampbellsoup]

Do you want to link to e.g. https://datatracker.ietf.org/doc/draft-linuxgemini-otpauth-uri/

[coveralls]

coverage: 95.746% (+0.001%) from 95.745%
when pulling d83533d on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into 2a98828 on pennersr:main.

[coveralls]

coverage: 95.746% (+0.001%) from 95.745%
when pulling d83533d on mecampbellsoup:mc/mfa/add-totp-url-to-headless-resp-data
into 2a98828 on pennersr:main.

[mecampbellsoup]

@pennersr this one ready to go now I think! 🙏

NOW it should be ready 😆