boldprogressives/django-htauth

A Django auth backend that uses credentials stored in an .htpasswd file.

django-htauth's Issues

Writing to htpasswd files

Right now the library only reads from htpasswd files; it can't write to them when you add a new user through the Django admin.

This is arguably a feature.

However, it should be possible to write to the htpasswd files if you want to, maybe with a setting.

Read htgroup files

The library should be able to read .htgroup files as well as .htpasswd files. Upon successful login it would look through any .htgroup files that have been configured in settings.py and assign local Django auth.Groups to the user.

Open questions:

• Should it create these groups if they don't exist?
• Should it assign groups to the user on every login, or only on first login (i.e. if the user itself is being newly created)?

Possibly the different behaviors here could be configurable settings.

Don't always make every htauth user a superuser

Right now when a user logs in through the htauth backend, she's marked as both staff and superuser.

Instead (particularly after implementing htgroup support, #1) the user should not be marked as a superuser -- except, perhaps, if the user is in some specially-flagged htgroup entry that denotes superuser status.

I think the user should still be marked as staff though. Or possibly this behavior should be a configurable settings, HTAUTH_USERS_ARE_STAFF = True.