I followed the moodle Docs step by step guide on http://docs.moodle.org/en/Moodle_Network.
After clicking the network servers block link to the other moodle, it displays "You do not have permission to begin a remote session."
What could be the reasons for that?
Hi Isuru,
Have you configured your Moodles "peer-to-peer", so that you can navigate from A to B and B to A?
Recently I was getting a "You do not have permission to begin a remote session" error clicking on the Network Servers link on the one Moodle and a "RPC payload not encrypted error" if I clicked on the Network Servers link on the other.
I was wondering if you are having the same problem?
Cheers,
Ian.
Have you configured your Moodles "peer-to-peer", so that you can navigate from A to B and B to A?
Recently I was getting a "You do not have permission to begin a remote session" error clicking on the Network Servers link on the one Moodle and a "RPC payload not encrypted error" if I clicked on the Network Servers link on the other.
I was wondering if you are having the same problem?
Cheers,
Ian.
Hi Ian,
I didn't get that latter error though, both were "You do not have permission to begin a remote session".
and when you mentioned configuring "peer-to-peer", where can I find it?
If you meant, Networking -> Peers; I added the remote host there and configured the services tab, enabled moodle network authentication and set roam to a remote moodle. But I get that error.
Thanks.
I didn't get that latter error though, both were "You do not have permission to begin a remote session".
and when you mentioned configuring "peer-to-peer", where can I find it?
If you meant, Networking -> Peers; I added the remote host there and configured the services tab, enabled moodle network authentication and set roam to a remote moodle. But I get that error.
Thanks.
Hi isuru,
Was the error generated by the originating moodle (identity provider), or the destination moodle (content provider)? (you can tell this from the URL that outputs the error, or by looking at the theme of the page etc.
What was the URL displayed in your browser's navigation bar when the error came up?
What versions of moodle are you running (both on the id provider, and content provider)?
In the absence of all the above information, I'd hazzard a guess that the problem lies in the mnetlogintoremote permission.
This is (partly) covered in point 2, subpoint 4 of http://docs.moodle.org/en/Moodle_Network
You need to make sure that the user you want to be able to jump to the remote moodle has this permission at the system context in the local moodle.
For testing purposes, I give this permission to authenticated user role, and this seems to do the trick. I don't think there are any nasty security problems with this.
Pete.
Was the error generated by the originating moodle (identity provider), or the destination moodle (content provider)? (you can tell this from the URL that outputs the error, or by looking at the theme of the page etc.
What was the URL displayed in your browser's navigation bar when the error came up?
What versions of moodle are you running (both on the id provider, and content provider)?
In the absence of all the above information, I'd hazzard a guess that the problem lies in the mnetlogintoremote permission.
This is (partly) covered in point 2, subpoint 4 of http://docs.moodle.org/en/Moodle_Network
You need to make sure that the user you want to be able to jump to the remote moodle has this permission at the system context in the local moodle.
For testing purposes, I give this permission to authenticated user role, and this seems to do the trick. I don't think there are any nasty security problems with this.
Pete.
Hi Peter,
Umm. Am I right in thinking that if Isuru didn't have mnetlogintoremote set to Allow then he wouldn't see the Network Servers block?
Cheers,
Ian.
Umm. Am I right in thinking that if Isuru didn't have mnetlogintoremote set to Allow then he wouldn't see the Network Servers block?Cheers,
Ian.
Hi all,
The errors are provided by the destination.
They were both "You do not have permission to begin a remote session" before, but now changed as follows,
The errors are,
http://10.16.70.160/moodle/auth/mnet/land.php?token=274db9d6d3ca12ba89b7dfae0d351e81e21dab38&idp=http://localhost/moodleucsc&wantsurl=
(This is the "You do not have permission to begin a remote session." error)
and
http://10.16.70.161/moodleug1.9/auth/mnet/land.php?token=364e21bbb415e90b5546c8c1da049acc3adb7102&idp=http://10.16.70.160/moodle&wantsurl=
(This is the "RPC auth/mnet/user_authorise:Payload not encryptedERROR 1:1:Payload not encrypted" error)
I'm using moodle 1.9.1 and 1.9.2 on the 2 ends.
I have set the roam option to 'Allow' for 'Authenticated user'.
As Ian mentioned, I think this is also his problem also.
Thanks.
The errors are provided by the destination.
They were both "You do not have permission to begin a remote session" before, but now changed as follows,
The errors are,
http://10.16.70.160/moodle/auth/mnet/land.php?token=274db9d6d3ca12ba89b7dfae0d351e81e21dab38&idp=http://localhost/moodleucsc&wantsurl=
(This is the "You do not have permission to begin a remote session." error)
and
http://10.16.70.161/moodleug1.9/auth/mnet/land.php?token=364e21bbb415e90b5546c8c1da049acc3adb7102&idp=http://10.16.70.160/moodle&wantsurl=
(This is the "RPC auth/mnet/user_authorise:Payload not encryptedERROR 1:1:Payload not encrypted" error)
I'm using moodle 1.9.1 and 1.9.2 on the 2 ends.
I have set the roam option to 'Allow' for 'Authenticated user'.
As Ian mentioned, I think this is also his problem also.
Thanks.
Hi Isuru,
That's exactly the same problem I had. There is probably a much better solution but... (brace yourselves everyone) the only way we could fix it was to drop the mnet tables and replace them with clean tables
.
If someone could post a solution to this problem without having to flatten database tables then I, for one, would welcome it with open arms
Cheers,
Ian.
That's exactly the same problem I had. There is probably a much better solution but... (brace yourselves everyone) the only way we could fix it was to drop the mnet tables and replace them with clean tables
.If someone could post a solution to this problem without having to flatten database tables then I, for one, would welcome it with open arms
Cheers,
Ian.
Hello
I am having the same problems. Is there a solution out there?
Tim
I am having the same problems. Is there a solution out there?
Tim
The thing that worked for me is that apache was not generating the key for a new certificate, so that was something outside of moodle but moodle needed that encryption certificate to pass along to the other moodles in the network. I don't know if that applies to anyone here, although I saw messages (i.e. Payload and parsing errors) like the ones you've noted in this this thread. Here are links to 2 other moodle forum discussions that helped me: http://moodle.org/mod/forum/discuss.php?d=83808 and http://moodle.org/mod/forum/discuss.php?d=75556. I'm using xampp apache, so there is a /xampp/apache/makecert.bat file that enables apache to generate the keys. You can open the makecert.bat file to see what it's doing if you're not on xampp.
Theresa
Theresa