scara / moodle-repository_cmis

CMIS repository plugin for Moodle
GNU General Public License v3.0
1 stars 3 forks source link

Repository does not support the improved repository functionality #1

Open DBezemer opened 11 years ago

DBezemer commented 11 years ago

One thing that would make this plugin much more usable then the standard Alfresco respository would be support for the improved file handling, as described on: http://docs.moodle.org/dev/Improved_support_for_external_File_content#File_manager_to_handle_virtual_files

would it also be possible to allow URL linking without the need to sign in (ie: pass a username/password within the plugin)?

DBezemer commented 11 years ago

In clarification: I mean the FILE_REFERENCE functionality.

After testing this plugin I am impressed by the quality of your work, everything works as advertised :) Great job so far!

scara commented 11 years ago

@DBezemer,

  1. URL linking and credentials: unfortunately it's out of CMIS control, the behaviour is strictly linked with the external repo (here Alfresco)
  2. FILE_REFERENCE is in the TODO list: it should overcome the limits of (1) by using a set of credentials to be used on-behalf-of, to let the local cached copy be successful

Spare time permitted, I'll change the priority in the TODO list to focus first on (2).

Thanks, appreciated! Matteo

DBezemer commented 11 years ago

I think (2) largely removes the need for (1) as well, if you need any support let me know, I'd be happy to help you out testing/bugfixing.

scara commented 11 years ago

Agreed. The next level could be to adopt OAuth to enforce the security of the authentication avoiding to pass username and password via HTTP Basic Authentication in every CMIS call but the PHP library provided by the Apache Chemistry project doesn't support it (yet?). Moreover I would like to make some investigations about CMIS repos supporting OAuth too when opening the CMIS session, at least two of them have this extended support: indeed the CMIS v1.0 spec doesn't make an explicit (see RFC 5023, §14) mention of OAuth while v1.1 does it (§5.2.9.2).

I'll keep you updated via this issue. Matteo