Produits Entr'ouvert » Authentic 2

I am not sure about this request; is this about completely removing django-registration dependency, or is this about refactoring authentic2/registration_backend/ in some way that the dependency would become optional?

If we're set on removing it, let's define requirements, on top of what django-registration did?

It has ~four views, register, and registration_complete, activate, and activation_complete. The workflow is this one:

1. User signs up, inactive account is created.
2. Email is sent to user with activation link.
3. User clicks activation link, account is now active.

Do we recreate the exact same thing?

At least, considering certivox, it would need an additional hook at the "user signs up" step, to validate that the request is ok.

Another requirement for a rewrite of this is that the "next" parameter of the login page should be conserved through the whole registration process so that the registration workflow at the IdP can be integrated into the login workflow of any service provider.

In a discussion about Vincennes, it was noted they would like the possibility to have an email sent to the site admins whenever a new user registers.