Go to APIs & Services on the left hand tab (see image below).Then select OAuth Consent screen page.Under OAuth Consent screen select either Internal or External
Companies with a Google Workspace should choose Internal
Otherwise choose External
On the next page:
Provide an app name (can go with RECAP)
Provide any email you own (or meet@RECAP.work if you want us to handle questions from your RECAP users)
Upload the RECAP logo (or leave blank)
The Developer contact information can be any email you own (or again, meet@RECAP.work)
Leave the optional fields blankClick SAVE AND CONTINUELeave the next two pages for Scopes and Test users blank.
Still under APIs & Services, go to Credentials on the left hand barClick on +CREATE CREDENTIALS and choose OAuth client IDSelect Web application then call it RECAPAdd a Authorized JavaScript origins as:
http://localhost:3000 for local or replace with https://<WEB_DOMAIN> (e.g. https://www.RECAP.ai) if setting up for prod.
Add a Authorized redirect URIs as:
http://localhost:3000/auth/oauth/callback for local setup or https://<WEB_DOMAIN>/auth/oauth/callback if setting up for prod.
Click CREATE and save the Client ID and Client Secret for use in the next section
OAuth is controlled by 3 environment variables, regardless of deployment choice
(non-containerized, docker compose, kubernetes). To turn the feature on set:
AUTH_TYPE=google_oauth
OAUTH_CLIENT_ID=<your client id from above>
OAUTH_CLIENT_SECRET=<your client secret from above>
If setting up in production, then:
WEB_DOMAIN=<your domain including protocol e.g. https://www.RECAP.ai>
Kubernetes deployment was designed for production use and assumes that user Auth is a required feature therefore it is
on by default. To set up the required values, replace the REPLACE-THIS values in secrets.yaml with thebase64 encoded
client ID and client secret from above.