How to create Client ID & Client Secret Key for Documents Sharing Plugin?

For creating the Client Id & Client Secret Key for Documents Sharing Plugin, follow the below mentioned steps:

1. Go to https://console.cloud.google.com/cloud-resource-manager & sign in with your google account.
After that, Click on “New Project” for creating the Project. (For project name, don’t include space or special characters.)

2. Then select the created Project from the above dropdown in the header.

3. Go to “Library” from the left sidebar menu & Enable “Drive API” to activate the Drive API Services

4. After that go to the “Credentials” on the left sidebar menu.

5. Now click on “Create Credentials” and select “OAuth client ID”.

6. To create an OAuth Client ID we must first need to set a product name on the consent screen. To do so,Click on “Configure Consent Screen” and fill all the required details.

7. After configuring the consent screen, Select “Web Application” in the Application type. Fill the required details like name of the web application & authorized redirect URIs.
Format for Authorized redirect URIs: https://my-website/admin/edocument/settings

8. Now open the Web Application you have created & copy the “Client ID” & “Client Secret Key”.

9. After that you need to verify your app from the OAuth Consent Screen as explained here under “Verification for apps” section: https://support.google.com/cloud/answer/7454865

10. After activating the plugin, Paste the copied Client ID & Client Secret key with the Email Id (From which you have created the API keys) in the admin panel under Global Settings of the plugin & click on “Save Changes” button.

11. After clicking on the Save Button, you will get redirected to the gmail sign in screen from where you have to login with your Gmail Account details & grant various permissions of the website such as to see, edit, create and delete all the Google Drive Files created by the users on your website.

12. You will get redirected to the Global Settings again & after that click on the “Save Changes” button once again to make the API keys run well.

Watch Video