Code

Opened 3 years ago

Closed 3 years ago

#16030 closed New feature (wontfix)

Seperate Admin and User auth table

Reported by: dfcode Owned by: nobody
Component: contrib.auth Version: 1.3
Severity: Normal Keywords: admin,auth,database,table,router
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX:

Description

It would be killer if admin users and all other users didn't share the same auth_users table. In fact, I it would be nice if they weren't in the same package at all. Maybe auth and auth_admin. This would allow us to utilize the database router to share users with other projects/schemas, without breaking the admin.

Attachments (0)

Change History (1)

comment:1 Changed 3 years ago by lukeplant

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

I think this is going to have to be WONTFIX. For every use case where your preference makes sense, there will be others where the opposite does. For example, when you want to move someone from being a 'non-admin' user to being an 'admin' user, it is obviously far more convenient in every way if you don't have to move rows from one table to another, but simply flip a boolean column.

I'm not sure what your requirements are, but if you have 'other users' who will never need to use the admin, what is stopping you creating your own User class, that is routed as you see fit, and using that for authorization for those users?

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.