Moodle Sarea

MoodleDocstik
Hona jauzi:nabigazioa, bilatu

Oharra: Itzuli gabekoak. Anima zaitezte eta ekin!.     (itzuli gabeko beste orri batzuk)

Moodle 1.8

Orokorra

Moodle Sarea Moodle-ren 1.8 bertsioak ekarri duen funtzio berria da. Sarearen funtzioak aukera ematen dio Moodle-ren kudeatzaileari beste Moodle batetiko esteka ezartzeko eta Moodle horretako erabiltzaileekin hainbat baliabide konpartitzeko.

Moodle Sarearen lehen bertsioa Autentifikazio Plugin berri batean oinarritzen da eta horrek egiten du posible saio hasiera bakarra Moodle-etan. Mikel erabiltzaile-izena duen erabiltzailea bere Moodle zerbitzarian izena ematen du normal eta beste Moodle zerbitzari batera eramango duen esteka bati sakatzen dio. Normalean, urrutiko Moodle-n bisitariaren baimenak bakarrik izango ditu baina azpitik saio hasierak autentifikatutako erabiltzailearen saioa ezarri du Mikelentzat urrutiko gunean.

KONTUZ: Moodle Sareak xmlrpc erabiltzea eskatzen du. Mesedez, jo zure phpinfo orrira hau erabiltzeko interesa baduzu eta bilatu --with-xmlrpc. Zure php ez badago xmlrpc-rekin konpilatuta lehenik horri ekin behar diozu! Momentuz badirudi PEAR xmlrpc ez dabilela.

Moodle Sarearen ezapenak hemen: Kudeaketa>Erabiltzaileak >Autentifikazioa>Moodle Sarea

Segurtasuna

Moodle Sarea funtzioak derrigorrez eskatzen du zure zerbitzariak Curl eta OpenSSL luzapenak instalatuta izatea. Moodle 1.8 instalatzean edo eguneratzean, zure zerbitzariak beste Moodle batzuekiko enkriptatutako komunikaziorako OpenSSL zertifikatu berria sortuko du, eta ondoren hilero (gutxi gora behera) aldatuko ditu enkriptazio-klabeak.

Komunikazioa XML-RPC transporte batean gertatzen da, eta XML-RPC dokumentuak lehenik XMLDSIG (XML sinadura digitala) gutun azal batean biltzen dira, eta ondoren XMLENC (XML enkriptazioa) gutun azal batean. Guztia PHPn enkriptatzen da, eta ez du https (Apache SSL) zerbitzaririk behar.

Erreferentziak:

A special mode can be enabled which would allow a machine with a specified IP address to make calls to the XML-RPC layer without using either encryption or signature envelopes. This mode is provided to enable Moodle to communicate with other software systems in which the integration of signatures and encryption might be prohibitively difficult. It is not envisioned that unencrypted inter-Moodle networking will ever be enabled.

Berdinen arteko Sarea

Sistemaren oinarrizko diseinua da hau. Oso erabilgarria izan daiteke Moodle bat fakultatez edo atalez abian jartzeko, bakoitzak bere erabiltzaileak kudeatzen dituela, eta aldi berean erabiltzailee Moodle instalazioan barrera ibiltzen utziz... ikataroko baimenen menpean.

Ezarpenak

Jarraipideek bi Moodle instalaziori dagozkio: MoodleA eta MoodleB. Biek egon behar dute egoki instalatuta eta ez dute inoiz aldez aurretik Moodle Sarea konfiguratuta izan behar.

Oharra: Arazoak baldin badituzu, ziurtatu arazketa gaituta duzula Gunearen kudeaketa > Zerbitzaria > Arazketan. Aparteko diagnosi-mezuak erakutsiko dira (bereziki Moodle 1.9.2-tik aurrera)

  1. Get them to talk to each other
    1. Ensure Admin > Server > Environment indicates you have curl installed
    2. If MoodleA and MoodleB are hosted in the same domain, ensure they have a different cookie prefix. Note that changing the cookie prefix will log you out! You can change the cookie prefix via Admin > Server > Session Handling.
    3. On both, go to Admin > Network > Settings and turn Networking ON.
    4. On MoodleA go to Admin > Network > Peers - put the URL of MoodleB under "Add New Host" and click Add.
    5. Do the equivalent on MoodleB.
  2. Get user roaming going
    1. On both, go to Admin > Users > Authentication and enable Moodle Network authentication plugin. Click on 'Settings' and enable auto_add_remote_users.
    2. On MoodleA go to Admin > Network > Peers, click on 'MoodleB', and click on 'Services'. Enable SSO-IDP publish and subscribe, and SSO-SP publish and subscribe.
    3. Do the equivalent on MoodleB.
    4. On both, go to Admin > Users > Permissions > Define Roles, only roles that have "Roam to a remote Moodle moodle/site:mnetlogintoremote" will be allowed to roam. Grant the privilege as appropriate.
    5. On both, go to the homepage, and add the 'Network Servers' block.
    6. To test, it is recommended to use a different browser (even on a different machine) that is logged in to neither. Login to MoodleA with a non-administrator account that has the permissions to roam. You should see the Network Servers block, and clicking on it you should go to MoodleB with a newly autocreated account.
  3. Get remote enrolments going -- this is optional. It allows administrator of MoodleB can enrol users that are "native" to MoodleB in courses in MoodleA, and viceversa.
    1. On both, go to Admin > Courses > Enrolment and enable Moodle Network enrolment plugin (click Save). Click on 'Edit' and enable 'allow_allcourses' or select some courses or categories to be remotely enrolled.
    2. On MoodleA go to Admin > Network > Peers, click on 'MoodleB', and click on 'Services'. Enable Enrolment publish and subscribe.
    3. Do the equivalent on MoodleB.
    4. To use, in MoodleA go to Admin > Networking > Enrolments. You will see MoodleB listed. Click on MoodleB and you will see a list of courses that MoodleB offers for remote enrolment. Select the course you want, and then enroll the users you want to that course.

Erabilera

Konektatu Komunitate-zentro batekin

A Community hub is a Moodle server that is configured to accept connections from other Moodle servers, and to provide a set of services to users of these other servers. This guideline will direct you to connect to a Community hub, assess the services it has to offer, and enable those services for your users.

Setup

  1. Get talking to the Hub
    1. Ensure that the Admin > Server > Environment page indicates you have curl and openssl installed
    2. Go to Admin > Network > Settings and turn Networking on
    3. Go to Admin > Network > Peers and enter the URL of Community Hub under "Add New Host". Click Add
    4. The host details for the Community Hub should appear with the Site Name field already populated. Click Save changes
    5. The details will be written to your database and two new tabs will appear in this window: 'Services' and 'Logs'. Click Services
    6. A list of services will appear, each with a checkbox for 'publish' and 'subscribe'. Check the checkboxes for any services you want to publish or subscribe to

Erabilera

If the Community Hub has already enabled a service for you, there will be a tick alongside the appropriate checkbox, for example: if the Hub is publishing Moodle Networked Enrolment, then a tick will appear alongside the subscribe checkbox for this service. Note that in order to enable some functionality, prominently single-sign-on, you may have to publish a service, e.g. the Identity Provider service. The Community Hub will access this service on your Moodle, asking it to authenticate your users.

  1. Enable Roaming
    1. Subscribe to SSO (Service Provider) by checking the box
    2. Publish SSO (Identity Provider) by checking the box
    3. Click Save changes
    4. Go to Admin > Users > Permissions > Define Roles, and grant the capability Roam to a remote Moodle moodle/site:mnetlogintoremote to an appropriate role
    5. Go to Admin > Users > Authentication and enable the Moodle Network authentication plugin
    6. Go to your homepage, turn on editing, and add the 'Network Servers' block
    7. Using a different web-browser, log on as a non-admin user who inhabits the role you granted the roaming capability to
    8. Note that the Community Hub is listed in the Network Servers block on the homepage. Click on the link to that server
    9. Some of your user details will be transferred to the Community Hub server, and a browsing session will be started for you as if you had logged on there directly
  2. Enable Networked Enrolment
    1. Return to the web browser you've been using as the site administrator
    2. Go to Admin > Network > Peers and click on the entry for the Community Hub.
    3. Click on the Services tab
    4. Subscribe to Moodle Networked Enrolment
    5. Go to Admin > Courses > Enrolment and enable the Moodle Network enrolment plugin. Click Save changes
    6. Click on edit to view the details for networked enrolments.
    7. Go to Admin > Networking > Enrolments to see a list of Moodle servers that offer this service to you
    8. Click on a server name to view a list of courses that the server offers to your users
    9. Click on a course name, to view a list users that you can enrol in this course
    10. Enrol users
    11. Profit!

Running a Community hub

A Community hub is a regular Moodle site that runs in a special mode. As a Moodle Administrator, when you add another Moodle site to your list of network peers, your Moodle will contact that site to find out what it is called, and to request its public key for encrypted communication. Normally, the remote server will simply provide this information without making any record of the transaction.

A Community hub is different. As soon as you add an entry for a Community hub to your system, the Community hub will create an entry for your server in its list of hosts, and may immediately begin to offer services to the users of your site.

This section will guide you to set up a Community hub, and select services to offer to all comers.

Setup

  1. Enable Networking
    1. Ensure that the Admin > Server > Environment page indicates you have curl and openssl installed
    2. Go to Admin > Network > Settings and turn Networking on
    3. Go to Admin > Network > Peers and tick the checkbox for Register all hosts. Click on Save Changes
    4. On the same page, the first entry in your list of hosts should be All hosts. Click this link
    5. Click on Services and enable any services you want to offer to all comers

Ikusi halaber

"https://docs.moodle.org/all/eu/index.php?title=Moodle_Sarea&oldid=12123"(e)tik jasota
Powered by MediaWiki