id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
24874	"Why does ""AbstractBaseUser"" contain ""password"" and ""last_login"" fields?"	Christopher D'Cunha	nobody	"Why does ""AbstractBaseUser"" contain ""password"" and ""last_login"" fields?

The [https://github.com/django/django/blob/master/django/contrib/auth/base_user.py#L1-L4 module docstring] and the [https://docs.djangoproject.com/en/1.8/topics/auth/customizing/#specifying-custom-user-model documentation] suggest that AbstractBaseUser should be inherited when creating custom user models. Why are these attributes expected to be common to all custom user models?

My immediate use case is that I want a custom user model for a delegated auth setup (Opend ID Connect in my case), so I don't have any passwords and last_login per se. At the same time, I'd like to use a ""Django supported"" base user model to know that I support the exact API that the User model needs. The only way I can see to do this is to re-implement AbstractBaseUser without these fields."	Cleanup/optimization	closed	contrib.auth	1.8	Normal	invalid			Unreviewed	0	0	0	0	1	0