[GH-ISSUE #47] 2factor auth #46

Open
opened 2026-02-26 09:35:10 +03:00 by kerem · 7 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/47

ThomasWaldmann wrote:
later add 2factor auth, TOTP, QR-Code rendering.

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/47 ThomasWaldmann wrote: later add 2factor auth, TOTP, QR-Code rendering.
Author
Owner

@ThomasWaldmann commented on GitHub (Jan 26, 2014):

note: before any local 2factor auth is implemented, you could already use the 2factor auth of some social auth (like google auth with 2FA) that we already offer.

<!-- gh-comment-id:33320322 --> @ThomasWaldmann commented on GitHub (Jan 26, 2014): note: before any local 2factor auth is implemented, you could already use the 2factor auth of some social auth (like google auth with 2FA) that we already offer.
Author
Owner

@elnappo commented on GitHub (Oct 29, 2014):

https://github.com/Bouke/django-two-factor-auth

<!-- gh-comment-id:60898557 --> @elnappo commented on GitHub (Oct 29, 2014): https://github.com/Bouke/django-two-factor-auth
Author
Owner

@ThomasWaldmann commented on GitHub (Oct 29, 2014):

Looks nice. :)

<!-- gh-comment-id:60918532 --> @ThomasWaldmann commented on GitHub (Oct 29, 2014): Looks nice. :)
Author
Owner

@elnappo commented on GitHub (Oct 30, 2014):

we might combine it with https://github.com/Bouke/django-user-sessions ?

<!-- gh-comment-id:61077034 --> @elnappo commented on GitHub (Oct 30, 2014): we might combine it with https://github.com/Bouke/django-user-sessions ?
Author
Owner

@ThomasWaldmann commented on GitHub (Oct 30, 2014):

maybe. for each extension we add, we always have to consider how well it is maintained (now and in future), because as we have already seen with "registration", things get awful if a new django comes out and the extensions suddenly and unexpectedly fails.

<!-- gh-comment-id:61093523 --> @ThomasWaldmann commented on GitHub (Oct 30, 2014): maybe. for each extension we add, we always have to consider how well it is maintained (now and in future), because as we have already seen with "registration", things get awful if a new django comes out and the extensions suddenly and unexpectedly fails.
Author
Owner

@stevleibelt commented on GitHub (Mar 29, 2023):

Hey there,

How is the status of this issue? Is there anything that prevents us/you from implementing this feature?

Best regards,
Stev

<!-- gh-comment-id:1488475874 --> @stevleibelt commented on GitHub (Mar 29, 2023): Hey there, How is the status of this issue? Is there anything that prevents us/you from implementing this feature? Best regards, Stev
Author
Owner

@ThomasWaldmann commented on GitHub (Mar 29, 2023):

No, but updating the code to recent django (see PRs) and keeping out scammmers / letting in legitimate users has higher prio right now.

<!-- gh-comment-id:1488482073 --> @ThomasWaldmann commented on GitHub (Mar 29, 2023): No, but updating the code to recent django (see PRs) and keeping out scammmers / letting in legitimate users has higher prio right now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#46
No description provided.