--
Ticket URL: <https://code.djangoproject.com/ticket/24567>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
This is expected behavior. Please see the
[https://docs.djangoproject.com/en/1.8/topics/auth/default/#id7 auth
documentation].
Also note: if you want a user account to be able to create users using
the Django admin site, you’ll need to give them permission to add users
and change users (i.e., the “Add user” and “Change user” permissions). If
an account has permission to add users but not to change them, that
account won’t be able to add users. Why? Because if you have permission to
add users, you have the power to create superusers, which can then, in
turn, change other users. So Django requires add and change permissions as
a slight security measure.
--
Ticket URL: <https://code.djangoproject.com/ticket/24567#comment:1>
Comment (by yoyoma):
Ah, I see. Thanks for the explanation, @timgraham.
Because the User create form includes only username and password fields
(no permission and staff/superuser fields), I wonder if it's worth
exploring the option of changing this (e.g., user with only "can add User"
permission adds a User with a username and password, is redirected back to
the User list view).
--
Ticket URL: <https://code.djangoproject.com/ticket/24567#comment:2>
Comment (by timgraham):
Maybe... I didn't research when that restriction was added to see if
things have changed since then.
--
Ticket URL: <https://code.djangoproject.com/ticket/24567#comment:3>