Cloud Repositories for Jaspersoft IO At-Scale

This chapter describes how Jaspersoft IO At-Scale can use reports and resources stored in the cloud repositories (Google Drive, Github, and Dropbox) using OAuth 2.0 standard protocol for authorization.

OAuth2 Repositories

By default, Jaspersoft IO At-Scale comes with three preconfigured OAuth2 repositories for Google Drive, Github, and Dropbox. Each of these is defined in the following folders:










To use these repositories, each repository configuration file needs to be updated with actual clientId and secretKey values. These values are obtained from the target cloud storage providers while registering your Jaspersoft IO At-Scale instance with them.

The configuration file for Google Drive repository will appear similar to the following:

<bean class="">
   <property name="jasperReportsContext" ref="baseJasperReportsContext"/>  
   <property name="googleDriveProvider">
      <bean class="">
         <property name="googleDriveFactory">
            <bean class="">
               <property name="clientId" value="put-client-id-here"/>
               <property name="secretKey" value="put-secret-key-here"/>
         <property name="serviceCache">
            <bean class="com.jaspersoft.jrio.common.execution.cache.LocalCacheAccessFactory">
               <property name="cacheContainer" ref="localCacheManager"/>
               <property name="cacheRegion" value="googleDriveServices"/>

Accessing Cloud Repositories

The sample web application helps you connect to the cloud repositories (Google Drive, Github, and Dropbox) by providing a login UI. You can access the sample cloud repository login UI if you have the required OAuth2 credentials, namely clientId and secretKey. These values need to specify in both repository configuration files and client application configuration file [JRIO_DOCS_WEB_APP]/WEB-INF/classes/

The sample web application acts as a proxy to the Jaspersoft IO At-Scale application and acquires the OAuth2 authorization tokens from the cloud services. Then these access tokens are passed to the Jaspersoft IO At-Scale, allowing Jaspersoft IO At-Scale to load reporting resources from the remote repositories.