From 5ee1c774ac5975780f446d26f019da31aab84abb Mon Sep 17 00:00:00 2001 From: Evarin Date: Sun, 3 Jun 2018 22:15:16 +0200 Subject: [PATCH] Better README display? --- README.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index d69d2b7..11c4195 100644 --- a/README.rst +++ b/README.rst @@ -179,15 +179,17 @@ Configuration Set ``SOCIALACCOUNT_ADAPTER='allauth_ens.adapter.LongTermClipperAccountAdapter'`` in `settings.py` + Auto-signup Populated data - username: ``@`` - email: from LDAP's *mailRoutingAddress* field, or ``@clipper.ens.fr`` - first_name, last_name from LDAP's *cn* field - extra_data in SocialAccount instance, containing these field, plus *annee* - and *promotion* parsed from LDAP's *homeDirectory* field (available only on - first connection) - + and *promotion* parsed from LDAP's *homeDirectory* field (available only on + first connection) + + Account deprecation At the beginning of each year (i.e. early November), to prevent clipper username conflicts, you should run ``$ python manage.py deprecate_clippers``. @@ -196,6 +198,7 @@ Account deprecation (using LDAP), so that a known user keeps his account, but a newcomer won't inherit an archicube's. + Customize You can customize the SocialAccountAdapter by inheriting ``allauth_ens.adapter.LongTermClipperAccountAdapter``. You might want to @@ -206,6 +209,7 @@ Customize ``get_username`` (as done in the example website) allows to get rid of that behaviour, and for instance attribute a default entrance year. + Initial migration If you used allauth without LongTermClipperAccountAdapter, or another CAS interface to log in, you need to update the Users to the new username policy,