Changes between Initial Version and Version 1 of AccountManagerPlugin/RegistrationInspector

Timestamp:

Aug 11, 2012, 1:51:09 PM (12 years ago)

Author:

Steffen Hoffmann

Comment:

create a dedicated page for this topic and move in content from wiki:AccountManagerPlugin/Modules

AccountManagerPlugin/RegistrationInspector

@@ +1 @@
+[[PageOutline()]]
+= New User Registration Process =
+
+== Involved Modules ==
+=== !RegistrationModule ===
+ '''Package''':: acct_mgr.web_ui
+
+Enables users to register a new account.  It adds a “Register” link on the same menu bar as the “Login” link.
+
+[[Image(AccountManagerPlugin:register.png)]]
+
+==== Configuration ====
+{{{
+#!cfg
+[components]
+acct_mgr.web_ui.RegistrationModule = enabled
+}}}
+
+> '''Warning:''' You must enable one of the [wiki:AccountManagerPlugin/AuthStores password storage modules] for the Registration Module to work.
+
+'''Note:''' You must not enable `ignore_auth_case` in `trac.ini` as otherwise this module won’t work. [''Update:'' This doesn't apply to `trunk` branch anymore. Use a revision at changeset [9286] or later to lift this limitation.]
+
+=== !EmailVerificationModule ===
+ '''Package''':: acct_mgr.web_ui
+
+If you enable this, users will be sent an email with a verification code to enter, to approve it is really their own email address:
+
+==== Configuration ====
+{{{
+#!cfg
+[components]
+acct_mgr.web_ui.EmailVerificationModule = enabled
+acct_mgr.notification.AccountChangeListener = enabled
+}}}
+
+Until they entered the verification code on the URL sent with the email, their permissions will be restricted (even if they have the TRAC_ADMIN privilege, they won't be able to access anything exceeding the standard privileges of ''authenticated'' users). ''Update:'' After changeset [9304] ACCTMGR_ADMIN (and TRAC_ADMIN, as it inherits it among all other privileges) won't be bothered with the verification procedure.
+
+This '''has been added as a strict requirement now''' as suggested by ticket #5509 to `trunk` code with changeset [9277], but was not enforced before, so verification only happened, if an email had been specified on registration. In other words, if some user registered w/o specifying an email address, this was possible and an unrestricted account was created without requiring further actions.
+
+Note that if you don't want to enforce entering a valid email on registration, you may want to disable this component. An option
+{{{
+#!cfg
+[account-manager]
+verify_email = false
+}}}
+for switching this off easily, to restore the old behavior of AccountManagerPlugin by default, is available since changeset [9304] as well.
+
+As shown in the configuration above, you'll have to enable the accountchangelistener component as well. Without it, verification emails will be silently ignored (but the webui will still say they got sent!).