django-allauth

Not implementing it yourself does not imply that you should use auth-as-a-service. There are plenty of auth libraries out there for your programming language of choice. Take a look at their source code and see how much stuff is in there to get a sense of why you should not implement your own. I use django-allauth: https://github.com/pennersr/django-allauth

Here is the link, for convenience: https://github.com/pennersr/django-allauth

Depends on the project: Firebase Authentication[1] is an excellent easy add on for apps (both Web and Mobile) that I want to get running quickly. It's free, scales, supports lots of social auth providers and can take care of email verification etc. When I'm building a website it really depends. Wordpress and Django have excellent inbuilt authentication and authorization systems. Djangos can be quickly expanded to support social providers with `django-allauth`[2] For everything else I use KeyCloak[3] - Red Hats open source Identity Provider/Single Sign On which supports oAuth2.0, OpenID Connect, SAML, themes etc. Documentation and support is relatively good but can be quite overwhelming especially if you're not used to the relevant standards (knowing the different flows in oAuth2.0 and which one you want to use). [Self plug]: I'm building

django-allauth also affected: https://github.com/pennersr/django-allauth/issues/2413

Oh gods please don't align like this, it's just so unreadable. Example of what that does in practice: Lines that end up wrapping almost at the end of the soft-character-limit and look like this: https://github.com/pennersr/django-allauth/blob/c9b31ddee81d...

Note to those who might be implementing multiple forms of authentication in a Django app: t some point, either through a popular boilerplate or by finding it online, you may be tempted to use https://github.com/pennersr/django-allauth to unify multiple authentication mechanisms. Be very, very careful before using this library. Not only do seemingly simple things require digging into the codebase and finding something to override or monkey-patch, but there are many ways in which denormalized data (such as a user's primary email address as a column therein, which is duplicative with a primary-marked row in a one-to-many table of user email addresses) can become desynchronized. It may still be the right choice for your business, but it comes with massive technical debt. Caveat emptor. If the self-rolled techniques in the OP are sufficient fo

Yes, Emacs used to group spaces into tabs. I think most editors these days do the right thing. This problem goes away if you indent parameters instead of aligning them: print( 'some long thing', further, arguments) In this case it takes an extra line, but it's often shorter.[1] [1] https://github.com/pennersr/django-allauth/blob/a44134688f5b...

Tabs for indentation; spaces for alignment; I don't know why you'd want to insert tabs in the middle of a line. Also, most people who do have several years of experience under their belt will tell you: don't align. Mid-line alignment is a waste of a maintainer's time to have to update alignment blocks every time you add/remove variables... and statement-alignment is unreadable[1]. [1] https://github.com/pennersr/django-allauth/blob/a44134688f5b...

> - Some types of alignments (specifically, method parameter alignment) create extreme horizontal noise. See for yourself: https://github.com/pennersr/django-allauth/blob/c9b31ddee81d.... The answer there would be to put the line break before the . and align the .dispatch under super.

Hey, a rationale, something I seldom see in those debates :) I think that if you do want to align, spaces are unavoidable. But I want to reiterate three points against alignment: - Alignment creates a maintenance burden. It has to be updated whenever you touch unrelated lines, which creates whitespace noise. - Some types of alignments (specifically, method parameter alignment) create extreme horizontal noise. See for yourself: https://github.com/pennersr/django-allauth/blob/c9b31ddee81d... That stuff's ridiculous. Styleguides are meant to make the code more readable and maintainable - this is neither. Method calls can be defined just like arrays, where the first argument goes on a newline with a single added indent. No need to align anything. - Finally, alignment breaks with proportional fonts. This is something someone else brought up on

Hah, those are beautiful examples, thank you! :) The latest I encountered was a few days ago in the allauth codebase, where I found several instances of things like these: https://github.com/pennersr/django-allauth/blob/07d70fd68c4c... I remember that page, actually. It's a really good point that code alignment breaks proportional fonts, I never considered it. More points for accessibility I suppose!

Sorry about your troubles. However, you can use Django AllAuth (https://github.com/pennersr/django-allauth) to achieve an email login system by tweaking its settings. Specifically: ACCOUNT_AUTHENTICATION_METHOD = "email" ACCOUNT_USERNAME_REQUIRED = False (if you do not want to use the username field) More here: http://django-allauth.readthedocs.org/en/latest/configuratio... Cheers!

Do you know how well cookiecutter-django [0] handles email logins? I've been meaning to play around with cookiecutter, but I haven't started a new project recently. Cookiecutter uses django-allauth [1], which seems to offer email login methods, from what I see in a cursory look at the docs [2]. [0] - https://github.com/pydanny/cookiecutter-django [1] - https://github.com/pennersr/django-allauth [2] - http://django-allauth.readthedocs.org/en/latest/configuratio...

Django-allauth supports Mozilla Persona. (has for a while now) https://github.com/pennersr/django-allauth#persona Its my preferred Django authentication solution. (much to my dismay when I want a profile app that doesn't bundle its own auth code. If you haven't had a look. Its worth taking one. :-)

I like django-allauth a lot for all the social authentication integration: https://github.com/pennersr/django-allauth