Session moodle

[mcassisa]

Added the authentication through Moodle session on the model of remote user (auth = none because it is assumed that authentication is already managed by moodle itself). In order to easily get the moodle's session (i.e. without any modification in moodle) , MRBS should be in a subdirectory.
The users that have the capability to create courses in a specified category in moodle ("moodle/course:create") - tipically this is true for teachers - are granted an Access level = 1 (further adjustments on this can be done to meet the diverse installation requirements)

[jberanek]

Thanks for this @mcassisa - we'll take a look at this and get back to you.

[campbell-m]

This looks useful. I have a few comments:

In AUTHENTICATION line 851 is

$auth['joomla']['rel_path'] = '..';   // Path to the Joomla! installation relative to MRBS.

I'm not familiar with Moodle. Is Joomla necessary to run it?

In systemdefaults.inc.php line 1047:

$auth['moodle']['rel_path'] = '..'; //MRBS should be in a subdirectory of moodle

Does the comment mean that MRBS has to be in a subdirectory of Moodle, or is this comment just explaining the '..' setting? Could you make the comment clearer please.

Also, the config settings and comments in AUTHENTICATION are not the same as those in systemdefaults.inc.php.

[mcassisa]

I fixed the documentation in AUTHENTICATION file and cleaned it up

[campbell-m]

I fixed the documentation in AUTHENTICATION file and cleaned it up

Thanks.

One other comment: does Moodle offer a user API so that you can get details of users other than the currently logged in user? That would enable you to create AuthMoodle.php with methods such as getUserFresh() and getUsernames().

[mcassisa]

Moodle offers some way to retrieve users, but apparently the operation is very heavy for large sites. What would the benefits to retrieve a list of moodle users?

[campbell-m]

Getting a single user's details, through getUserFresh(), would allow you to see a user's display name rather their username when viewing booking details. I assume that this operation is not database intensive.

Getting all the users, through getUsernames(), would allow admins to create bookings on behalf of other users by selecting them from a drop-down list of users. The drop-down is populated in the background by an Ajax call, so should not slow down MRBS. But you could always choose not to implement this and just do the single user case above.

[Neustradamus]

Any progress on this PR?

[mcassisa]

No, I didn't work on it in the meantime (we chose to manually create users) - the contribution is usable, although it can be further improved