|
|
| (3 intermediate revisions by 2 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. |
|
| |
|
| :Hopefully the extra sentence I just added makes things clear now ;-) --[[User:Helen Foster|Helen Foster]] 12:18, 26 June 2008 (CDT) | | :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) |
| | |
| ==Comments on re-organizing this page==
| |
| The primary authentication page is an introduction to this subject. Authentication is a menu item that only has sub menus in the administration block. Thusly, this page should be an introduction to this concept, outline each of the sub menus, have lots of links, not a lot of how to, a few examples of concepts, many references in See also (including FAQ link), and perhaps be the heading for link on a template called Authentication.
| |
| | |
| ===Chris's working notes===
| |
| | |
| Here are Chris's working notes that will form an introduction to Authentication. Typically, this will be no more than 3 sentences , with a second short paragraph that provides some context for breaking Authentication into sub menus, hopefully with a very simple example.
| |
| | |
| Definition: From authenticate and the greek "authentikos, 'principal, genuine'." or
| |
| *Authentication is the process of determining whether someone or something is actually who or what it asserts itself to be, the process confirms that the identification of the individual or data is accurate.
| |
| **Authorization is the process of determining what types of activities are permitted by a user. Usually, authorization is in the context of authentication: once you have authenticated a user, they may be authorized different types of access or activity.
| |
| **Roles are part of the authorization process that permits a user to perform certain activities. Permissions are specific task authorizations that a user may or may not be allowed to perform (inclucing viewing and changing).
| |
| **Enrolment in a course is acheived by assigning a role to a user in the course context.
| |
| | |
| '''Authentication, roles & permissions and enrolment'''. The authentication starts when a user enters a Moodle site. Most users think of the login screen as the first step in authentication of a user. After authentication, Moodle will give an initial set of authorizations to a user by assigning them an initial role. A user entering into a new or different context (for example a course) will assume certain permissions based upon their role which was given to them by some authorization process. A user who loses their authentication loses all authority and any previous roles.
| |
| ===Comments===
| |
| :Hi Chris, firstly a really big THANK YOU for your ideas and suggestions for the authentication documentation :-)
| |
| | |
| :Re. an introduction to authentication, I'd like to keep things as simple as possible. Isn't what we already have sufficient? ("... user authentication i.e. enabling people to login to your Moodle site").
| |
| | |
| :Re. the authentication submenus in Moodle, actually the number of submenus depends upon the number of plugins enabled on the manage authentication page.
| |
| | |
| :I suggested in the [[Talk:Manage authentication|manage authentication page comments]] that we only have one page for authentication/managing authentication, but after considering your authentication draft and comments, I can see the case for having two pages - [[Authentication]] (introduction and overview) and [[Manage authentication]] (setting the authentication method, common settings etc.).
| |
| | |
| :I suggest we keep the bulleted list of authentication methods on the authentication page, perhaps with a little explanation of each method, for example:
| |
| | |
| :*[[Manual accounts]] - accounts created manually by an administrator
| |
| :*[[No login]] - for preventing users from logging in
| |
| :*[[Email-based self-registration]] - for enabling users to create their own accounts
| |
| ::Good idea --[[User:chris collman|chris collman]] 10:56, 30 July 2008 (CDT)because we like to keep the overview as simple as possible as a best practice.
| |
| :What do you think of my suggestions? --[[User:Helen Foster|Helen Foster]] 07:56, 30 July 2008 (CDT)
| |
| | |
| :PS I'm not sure we need a template, as we have a [[:Category:Authentication]], and [[Authentication]] will also contain a list of authentication links. --[[User:Helen Foster|Helen Foster]] 08:00, 30 July 2008 (CDT)
| |
| ::That is fine for me. I forgot about the Category and the type of user should be a site administrator and not really a new user or reader of MoodleDocs by this time :) --[[User:chris collman|chris collman]] 10:56, 30 July 2008 (CDT)
| |
| | |
| == ACADEMIA DE TEATRO CINE Y TELEVISIO ==
| |
| | |
| Nuestra Corporacion tiene mas de 25 años de laborar en el campo del Teatro y la Tecnica audiovisual, coordina su actividad con el Ministerio de Cultura y el Museo de Arte de Pereira
| |
