Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Authentication.

Talk:Authentication: Difference between revisions

From MoodleDocs
(New page: I just added Guest Login Button (You can hide or show the guest login button on the login page) it's not clear if this just hides the button, or if hiding the button means that guest acces...)
 
(reply)
 
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
I just added Guest Login Button (You can hide or show the guest login button on the login page) it's not clear if this just hides the button, or if hiding the button means that guest access is effectively useless.
Hmm.. not sure if I did the right thing or not really. In the TOC there is a page Authentication common settings so I made that page and then removed from this Authentication intro page those common settings. I am just wondering if they should be together or not? This page here is an intro to all the authentication plugins but it also  relates to the Manage authentication screen in admin which is where authentication common settings are - so should all the stuff (updated) be here instead of my new page or not? Also - I copied and pasted some info about "data mapping" which I presume relates to different authentication plugins and would be on their settings pages - should that not actually go onto each settings page instead of here? Again not sure.
 
:How about we treat [[Authentication]] in a similar way to [[Enrolments]] i.e. have a short intro page listing the different authentication methods plus links to 'Manage authentication' (containing Authentication common settings info and info on multi-authentication) and [[Authentication FAQ]]. Re. Profile fields data mapping and locking, I agree it would be best copying and pasting to the authentication plugins for which it applies to. --[[User:Helen Foster|Helen Foster]] 03:42, 4 October 2011 (WST)

Latest revision as of 19:42, 3 October 2011

Hmm.. not sure if I did the right thing or not really. In the TOC there is a page Authentication common settings so I made that page and then removed from this Authentication intro page those common settings. I am just wondering if they should be together or not? This page here is an intro to all the authentication plugins but it also relates to the Manage authentication screen in admin which is where authentication common settings are - so should all the stuff (updated) be here instead of my new page or not? Also - I copied and pasted some info about "data mapping" which I presume relates to different authentication plugins and would be on their settings pages - should that not actually go onto each settings page instead of here? Again not sure.

How about we treat Authentication in a similar way to Enrolments i.e. have a short intro page listing the different authentication methods plus links to 'Manage authentication' (containing Authentication common settings info and info on multi-authentication) and Authentication FAQ. Re. Profile fields data mapping and locking, I agree it would be best copying and pasting to the authentication plugins for which it applies to. --Helen Foster 03:42, 4 October 2011 (WST)