Diff for /loncom/html/adm/help/tex/Domain_Configuration_Self_Creation.tex between versions 1.3 and 1.4

version 1.3, 2016/08/20 17:48:11 version 1.4, 2017/03/30 02:12:21
Line 38  log-in. Line 38  log-in.
 Self-created accounts with an e-mail address as username can be set to be queued for approval   Self-created accounts with an e-mail address as username can be set to be queued for approval 
 or created automatically. Institutional status types can be set to be self-reported for e-mail  or created automatically. Institutional status types can be set to be self-reported for e-mail
 type usernames -- set in the ``Default authentication/language/timezone/portal/types'' area --   type usernames -- set in the ``Default authentication/language/timezone/portal/types'' area -- 
 and processing (queued or automated) can be set, based on status.  and processing (queued or automated) can be set, based on status.  Note: self-reported status
   is collected from the query string in the original call to /adm/createaccount, from the type
   item (e.g., /adm/createaccount?type=student).  One way to gather this data would be to disable
   display of the ``New User?'' link on the log-in page, but instead create a separate portal page
   (e.g., replace the default /home/httpd/html/index.html) which would prompt new users to push a
   different button, depending on whether they were a student or an instructor, with the corresponding
   actions pointing at /adm/createaccount?type=$<$status type$>$, with $<$status type$>$ replaced with
   student or instructor.
   
 User information (in addition to e-mail address and password) can be set to be required, optional  User information (in addition to e-mail address and password) can be set to be required, optional
 or not requested.  or not requested.
   
 A Captcha mechanism can be used to validate that the user requesting a self-created account is  A Captcha mechanism can be used to validate that the user requesting a self-created account is
 a person, not a script.  There are two types of CAPTCHA to choose from -- the ``original'' CAPTCHA,   a person, not a script.  There are two types of CAPTCHA to choose from -- the ``original'' CAPTCHA, 
 which uses a self-contained perl module included with the LONCAPA prerequisites, or ReCAPTCHA,  which uses a self-contained perl module included with the LONCAPA prerequisites, 
 or ReCAPTCHA, which uses an external web service -- https://google.com/recaptcha --  or ReCAPTCHA, which uses an external web service -- https://google.com/recaptcha --
 and requires you to create an account and generate public and private keys which will be entered  and requires you to create an account and generate public and private keys which will be entered
 in the LON-CAPA domain configuration form.  If you have more than one server in your domain,   in the LON-CAPA domain configuration form.  If you have more than one server in your domain, 
 you should request ``global'' keys on the google.com/recaptcha site, as the same keys will be  you should request ``global'' keys on the google.com/recaptcha site, as the same keys will be
 used by the Account creation form's ReCAPTCHA on all servers in your domain.  used by the Account creation form's ReCAPTCHA on all servers in your domain. If using ReCAPTCHA, you
   can indicate whether version 1 or 2 should be used.
   

Removed from v.1.3  
changed lines
  Added in v.1.4


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>