User Mnet Hosts block: Difference between revisions
Line 20: | Line 20: | ||
Optional prerequisite : When using MNET and managing individual access, it may be worth to get consistant user profiles including custom fields. As access control fields used by User Mnet Hosts are custom fields, this makes sense. | Optional prerequisite : When using MNET and managing individual access, it may be worth to get consistant user profiles including custom fields. As access control fields used by User Mnet Hosts are custom fields, this makes sense. | ||
the patch discussed [http://tracker.moodle.org/browse/MDL-24549|here] proposes a simple patch to get user custom fields synchronization, pursuant they have been configured consistently in each MNET node. | the patch discussed [[http://tracker.moodle.org/browse/MDL-24549|here]] proposes a simple patch to get user custom fields synchronization, pursuant they have been configured consistently in each MNET node. | ||
Using this patch will allow users to bring their access allowance whereever they are in a Moodle Network. | |||
==Installing== | ==Installing== |
Revision as of 14:53, 6 October 2010
Moodle1.9
The User Mnet Hosts block (non standard) is similar to the Mnet Hosts block except it only gives access to MNET hosts where the user is allowed to jump to. Custom user profile fields will be used in a dedicated category to control which hosts are in the scope of the current user.
The block provides its own tools to install significant user custom fields and custom field catagory in Moodle so the MNET output can be controlled.
At its stage of developement, hiding a MNET in list of possible destination should not be considered as sufficiant in terms of security. These are not security doors, but a way to provide intelligible navigation to users depending on there profile.
A further securisation of the door is in developement plans.
Prerequisites
No mandatory prerequisites.
Optional prerequisite : When using MNET and managing individual access, it may be worth to get consistant user profiles including custom fields. As access control fields used by User Mnet Hosts are custom fields, this makes sense.
the patch discussed [[1]] proposes a simple patch to get user custom fields synchronization, pursuant they have been configured consistently in each MNET node.
Using this patch will allow users to bring their access allowance whereever they are in a Moodle Network.
Installing
Install the block as usual:
1. Unzip the block package within the blocks directory of your Moodle installation.
2. Browse to the Administration -> notifications menu.
Preparation
For the block to operate properly, you need generating relevant access field for each known MNET host in the neighbourhood. This is called synchronizing the block with the MNETwork configuration.
Settings
Global settings
Access to the synchronisation tool.
Instance settings
there are no instance settings.
Normal operations
Using a block instance
Just add an instance of this block instead of the standard Mnet Hosts block to limitate the network view to allowed targets.
Giving users access to an host
Edit the profile of users to check or uncheck the access fields matching the hosts you allow the user to see. You might change the custom fields settings for convenience so new users are implicitely allowed or disallowed for a particular host.