Ole Laursen a99aa32c59 Refactor account code to use the built-in Django signing framework ... (reusing code previously written for the community lists) instead of the a custom MD5 scheme, add tests of all views, rewrite custom form handling code to use plain forms and ensure that the data is properly validated and errors visible in the UI. Move help texts on the Person form up to the model. - Legacy-Id: 11136		2016-04-27 16:26:04 +00:00
..
migrations	Merged in personal/henrik/django-1.7@9020 which upgrades Django from 1.6.0 to 1.7.4 and applies the needed changes to the datatracker code to work with release 1.7.x.	2015-02-08 21:16:44 +00:00
.gitignore	Introduce initial authentication/authorization linkage. This has a	2007-05-23 16:10:32 +00:00
__init__.py	Remove shim layer from ietfauth, delete some dead code and migrate	2013-12-05 16:24:03 +00:00
forms.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00
htpasswd.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00
tests.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00
urls.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00
utils.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00
views.py	Refactor account code to use the built-in Django signing framework	2016-04-27 16:26:04 +00:00