couple of aspects:
- ietfauth.auth.EmailBackEnd is a django.contrib.auth backend to allow
two modified authentication methods:
- using email address (stored in django user table) as login username
- using htpasswd-style "crypt" passwords (for compatability with
existing user database). On the first successful login, the
password will be re-hashed to the django-hash style password.
- ietfauth.models.UserMap: a mapping from django user to IETF
person. This is configured as the profile table, meaning
that if you have a django user (e.g., from the RequestContext),
you can use user.get_profile.person to get to the IETF person.
- ietfauth.models has models for the "legacy" username/person mapping
tables (LiaisonUser aka "users" and WgPassword aka "wg_password").
This is to allow mapping of legacy permissions to django permissions
by walking these tables and applying permissions to users. The plan
is to discard these tables eventually.
- Legacy-Id: 155
* Moved RFCs model into idtracker
* Switched idtracker querys to use idinternal
* Created idinternal.document which returns either an InternetDraft or
an Rfc depending on the value of rfc_flag
* Create compatability methods in InternetDraft and Rfc models
to be able to use certain attributes in the template without
worring about where they come from.
Ticket #59 has a list of remaining bits.
- Legacy-Id: 98
