Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-42423

Google Drive integration with Sakai filepicker

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 20.0 [Tentative]
    • Fix Version/s: 20.0 [Tentative]
    • Component/s: cloud-storage, Content
    • Labels:
      None
    • Test Plan:
      Hide

      To test on experimental, where it is enabled: https://experimental.nightly.sakaiproject.org/portal
      If you enable the Google cloud provider, you will notice a new tab on the filepicker screen.

      1. The first time a user accesses that section, they'll have to click on the Configurate button in order to add their login data.
      2. They'll be redirected to the provider's login screen and, once validated and accepted, they'll be redirected back to a Sakai confirmation screen.
      3. From that point on, every time they enter that screen they will be able to browse, navigate, link or copy all their Google Drive files.
      4. If they click on Revoke, the account will be unlinked and they'll have to configure it again.
      5. The file and folder listing is cached in order to save calls to the API, but they can get the current status at anytime by clicking on the Refresh button.
      6. Google docs can't be downloaded (only exported or linked), so those won't show the Attach a file option.
      7. When a doc is linked and depending on the configured Google permissions, users will be able to access or request access to it.
      8. A small thumbnail appears on the right of each doc, it will be enlarged when the mouse steps over it.

      Show
      To test on experimental, where it is enabled: https://experimental.nightly.sakaiproject.org/portal If you enable the Google cloud provider, you will notice a new tab on the filepicker screen. 1. The first time a user accesses that section, they'll have to click on the Configurate button in order to add their login data. 2. They'll be redirected to the provider's login screen and, once validated and accepted, they'll be redirected back to a Sakai confirmation screen. 3. From that point on, every time they enter that screen they will be able to browse, navigate, link or copy all their Google Drive files. 4. If they click on Revoke, the account will be unlinked and they'll have to configure it again. 5. The file and folder listing is cached in order to save calls to the API, but they can get the current status at anytime by clicking on the Refresh button. 6. Google docs can't be downloaded (only exported or linked), so those won't show the Attach a file option. 7. When a doc is linked and depending on the configured Google permissions, users will be able to access or request access to it. 8. A small thumbnail appears on the right of each doc, it will be enlarged when the mouse steps over it.

      Description

      This is a development contributed by Pepperdine University, Duke University, University of Notre Dame and New York University, and developed by EDF.

      It consists of an integration of Google Drive with Sakai's filepicker, being able to browse, link or copy your own files to any tool that uses the filepicker. Besides, the API of this component is accessible from anywhere else so it could be integrated with other tools like Lessons or Samigo.

      The development has been included under the cloud-storage Sakai module, which already included OneDrive. Both integrations can be enabled at the same time

      In order to enable this integration, you need to register an APP on the Google developers portal.

      1.  Access https://console.developers.google.com/apis/dashboard using your Google account login.
      2. On the APIs and Services menu, click on "ENABLE APIS AND SERVICES".
      3. Select Google Drive API, enable.
      4. Access Credentials / Create Credentials / Id Oauth client.
      5. Click on Configure authentication screen, if you haven't done it before.
      6. Give the APP a name and Save.
      7. Select Web, give the Client a name.
      8. The redirect uri (Web) must match the one you add on your sakai.properties files, by default it is "https://YOUR-SERVER-URL/sakai-googledrive-tool".
      9. Click on "Save". Get the Oauth client ID and secret, as you'll have to set them on your sakai.properties (googledrive.client_id and googledrive.client_secret).

       

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bergarvi Bernardo Garcia Vila
                  Reporter:
                  bergarvi Bernardo Garcia Vila
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code