Use this method if you wish to authenticate as a specific user to access files and folders.
- Navigate to the Google Cloud Consoleand sign in with your organisational Google account,
- Select your project from the list.
-
Click APIs and Services in the sidebar.
You will now need to create an OAuth Consent Screen that will display when users attempt to authenticate using the app:
-
Setting up the OAuth Consent Screen
- Click OAuth consent screen in the sidebar
- Set user type to External
- Set your app name. It can be whatever you wish unless…
- If you intend to use the Google Vision Text Extractor name the application Federation Services-VisionTextExtractor/1.0 as that will affect the outcome of the vision tasks (Though those will only work if your project has a linked billing account and billing enabled).
- Set the support email as the one you used to log in
- At the bottom, fill in the support email address.
- The support email will be the email the user is directed to when they’re directed to authorise Federation Services to transfer data.
- Click Save and Continue
-
Set up scopes:
- Click Add Scope and check .../auth/drive
-
Create OAuth Credentials
- Return to the APIs and Services Dashboard.
- Click Credentials.
- Click Create Credentials.
- Click OAuth Client Id.
- On the next screen, select Web Application.
- Give the credentials a name.
-
Under Authorised Redirect URIs, add the
following:
http://{SIMFLOFY_SERVER}/3sixty-admin/authconn/oauthcb
For example. If you’re running Federation Services on a local machine http://localhost:8080/3sixty-admin/authconn/oauthcb
Note: For Manage In Place, the domain server has to be public server since Google Drive only supports public server or localhost.Note: 127.0.0.1 will not work, but localhost will. - Click Create.
- Your new credentials will appear under OAuth 2.0 Client IDs. Click the Download button on the right and retrieve the Client ID and Client Secret from the downloaded JSON file.