When using GitHub codespaces, how to setup Google Oauth for development
When using GitHub codespaces, how to setup Google OAuth for development/
KHi @2b|¬2b. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. 
K----------------------
To set up Google OAuth for development in Wasp, you'll need to create a Google OAuth App and provide Wasp with your client key and secret. Here's how you do it:
Please note that the URLs used for the Authorized redirect URIs should match the URLs where your application is running. If you're using GitHub Codespaces, you'll need to adjust these URLs to match the URL of your Codespace.
To set up Google OAuth for development in Wasp, you'll need to create a Google OAuth App and provide Wasp with your client key and secret. Here's how you do it:
- Create a Google Cloud Platform account if you do not already have one: Google Cloud Platform (https://cloud.google.com/)
- Create and configure a new Google project here: Google Cloud Console (https://console.cloud.google.com/home/dashboard)
- Search for **OAuth** in the top bar, click on **OAuth consent screen**.
- Select what type of app you want, we will go with External.
- Fill out applicable information on Page 1.
- On Page 2, Scopes, you should select . You can optionally search for other things, like
.email - Add any test users you want on Page 3.
- Next, click **Credentials**.
- Select Create Credentials.
- Select OAuth client ID.
- Complete the form
- Under Authorized redirect URIs, put in: >
- Once you know on which URL(s) your API server will be deployed, also add those URL(s).
- For example: >
- Once you know on which URL(s) your API server will be deployed, also add those URL(s).
- When you save, you can click the Edit icon and your credentials will be shown.
- Copy your Client ID and Client secret as you will need them in the next step.
.env.serverPlease note that the URLs used for the Authorized redirect URIs should match the URLs where your application is running. If you're using GitHub Codespaces, you'll need to adjust these URLs to match the URL of your Codespace.
KFor more detailed instructions, you can refer to the Wasp documentation (https://wasp-lang.dev/docs/auth/social-auth/google#3-creating-a-google-oauth-app).
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
KSorry @2b|¬2b, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Perhaps try again in 15mins?
2I guess this is something to do with GitHub CodeSpaces portforwarding
M@2b|¬2b did you manage to get Wasp working in GitHub CodeSpaces? And now you are trying to get Google OAuth working? What have you tried / what is not working?
You are probably on right track that this has sometihng to do with ports. And, callback URL from Google for sure.
@Vinny (@Wasp) might be able to help here also, he was just looking into Codespaces a couple days ago.
You are probably on right track that this has sometihng to do with ports. And, callback URL from Google for sure.
@Vinny (@Wasp) might be able to help here also, he was just looking into Codespaces a couple days ago.
Vtry changing the ports to public
Valso, make sure to add to your .env.server file and to .env.client with the URLs from the port forwarding tab
V
V