altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 4 Packages Projects Releases Wiki Activity
3022 commits 1 branch 0 tags 2.6 GiB
Commit graph

19 commits

Author SHA1 Message Date
Henrik Levkowetz 73f00aa920 Enabled the check for existing account, disabled when we started using self-service http password reset, but hadn't started creating accounts yet. Refactored the two confirm*() methods in ietfauth/views.py; they need the same processing, only the templates to use differ. 
- Legacy-Id: 4583
 2012-07-04 05:12:20 +00:00
Henrik Levkowetz 20f5d25fd4 Add another needed import missed in the merge. 
- Legacy-Id: 4581
 2012-07-04 04:26:11 +00:00
Henrik Levkowetz 8b224559a7 Fix missing import. 
- Legacy-Id: 4574
 2012-07-03 19:08:43 +00:00
Henrik Levkowetz b0016c0fe9 Minor cleanup. 
- Legacy-Id: 4520
 2012-06-27 08:31:15 +00:00
Henrik Levkowetz b2573a43aa Merged community tracking branch from esanchez@yaco.es, r3175-3679,3713-3830. 
[[Split portion of a mixed commit.]]
 - Legacy-Id: 4518.2
 2012-06-27 08:15:14 +00:00
Ole Laursen 980d4e6444 Move new schema models from redesign/ to ietf/ 
- Legacy-Id: 3855
 2012-01-24 17:17:24 +00:00
Ole Laursen e866d9d8a9 Fix name of cookie 
- Legacy-Id: 3718
 2011-11-28 17:50:29 +00:00
Ole Laursen b114e5e6cf Add simple view for setting testemailcc cookie when server is in test mode 
- Legacy-Id: 3716
 2011-11-28 17:19:45 +00:00
Ole Laursen 8153a1c130 Patch up to pass request object to send mail in the instances where 
it's possible (i.e. when not run in cron) in preparation for better
mail test handling
 - Legacy-Id: 3711
 2011-11-25 18:24:14 +00:00
Ole Laursen 5a4c23ea92 Merge with trunk 
- Legacy-Id: 3676
 2011-11-21 16:41:21 +00:00
Emilio A. Sánchez López 7207329b0b Add the 'new account' link in the left sidebar. 
Change urls from registration to account.
Fixes #719
 - Legacy-Id: 3553
 2011-10-31 11:32:57 +00:00
Henrik Levkowetz 3d23e924cc Use the right module name for the json module. 
- Legacy-Id: 3507
 2011-10-25 14:02:01 +00:00
Ole Laursen 5c5d534104 Add person foreign key on Role to link the role and person directly instead of through Email, this will allow us to use non-personal emails on roles 
- Legacy-Id: 3418
 2011-09-14 14:01:17 +00:00
Henrik Levkowetz 6c93e2553b Add htpasswd management functionality. 
- Legacy-Id: 3386
 2011-08-26 18:06:12 +00:00
Ole Laursen 03bed41630 Merged in changes from the conversion branch 
- Legacy-Id: 3187
 2011-06-28 18:20:20 +00:00
Ole Laursen 1bea94eb12 Change auth model for new schema to use Person rather than Email where email is not necessary, use Person for user profiles rather than the old unused profile class, use REMOTE_USER backend directly instead of custom backend, use group roles for authorization rather than Django groups, port/proxy code from using IESGLogin to the new model 
- Legacy-Id: 3151
 2011-05-25 12:33:24 +00:00
Henrik Levkowetz 266b7820d0 Merged from log:branch/2.00@2363: Current release branch head to trunk. 
- Legacy-Id: 2365
 2010-07-21 12:48:05 +00:00
Henrik Levkowetz cd030d3b43 Adding copyright notices to all python files 
- Legacy-Id: 716
 2007-06-27 21:16:34 +00:00
Bill Fenner 4a5a5b1d59 Introduce initial authentication/authorization linkage. This has a 
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
 2007-05-23 16:10:32 +00:00