Having struggled for several days to created a working MNet Hub as per the documentation here:
I have failed to make a network where I can implement single sign-on.
If anyone is willing to help me, I would be prepared to re-write the documentation on MHub to make it easier for others to do this too.
The effect of other options and situations on MNet functionality are, for me at least, unclear.
Take the following situation for example:
I have an MNet hub set up and "Moodle-A" as a peer. If I have "Email-based self-registration" enabled and "MNet authentication" I would expect that registering a new user on Moodle-A would actually put their registration data on the MNet Hub. But it doesn't - the user only exists on the Moodle-A server.
I have an MNet Hub and Moodle-A and Moodle-B set up as peers. Mary is allowed to access Moodle-A and Moodle-B. John is only allowed to access Moodle-A. I don't see how MNet Hub allows me to authorise access in this manner.
Some of the documentation I found seems to imply that perhaps a course needs to be available on the peer Moodles before peer-specific access can be applied.
Drop me a line here if you are willing to help me tackle this - I am sure there will be plenty of users who would be happy to have a clearer explanation of MNet too.
We are working heavily with Mnet (we are extending Mnet basic feature with webservices), so maybe we could be of some help. Drop me a line if you want to exchange emails.
Did anyone help you with this? I am also experiencing many problems.
I have followed the steps of the mnet documentation as much as I can.
I had to add the $CFG->opensslcnf = in my config page.
But when I try to save I always get the following if the dubugin is on :
Request for https://myfakemoodlesite.com returned unexpected resultLower in the page the current public key is empty.
If I print the error is seems to refer to curl error 51 : CURLE_PEER_FAILED_VERIFICATION
I'm not sure what else to try. Could the fact that both my moodles are on the same server be a problem?
Or that they have the same secruity certificate?