forgejo-lila/lila
1
0
Fork 0
Code Issues 50 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Google OAuth app verification and publishing #16

New issue
Open
opened 2026-04-19 07:23:31 +00:00 by forgejo-lila · 0 comments
forgejo-lila commented 2026-04-19 07:23:31 +00:00
Owner
Copy link

Context

The Google OAuth consent screen is currently in 'Testing' mode. Only explicitly added test users can sign in. Any other Google user gets an error.

What to do

Publish the OAuth consent screen in Google Cloud Console so any Google user can sign in.

Steps

  1. Go to Google Cloud Console > APIs & Services > OAuth consent screen.
  2. Complete the branding information (app name, logo, support email, etc.).
  3. Submit for verification if required (depends on scopes requested).
  4. Set publishing status to 'Production'.

Acceptance criteria

  • Any Google user can sign in without being manually added as a test user
  • No 'This app isn't verified' warning screen appears

Notes

The app only requests basic profile scopes (email, name). This should qualify for a simplified verification process. See: https://support.google.com/cloud/answer/15549049
Google OAuth credentials JSON is saved locally in Downloads/lila/ on the dev laptop.

## Context The Google OAuth consent screen is currently in 'Testing' mode. Only explicitly added test users can sign in. Any other Google user gets an error. ## What to do Publish the OAuth consent screen in Google Cloud Console so any Google user can sign in. ## Steps 1. Go to Google Cloud Console > APIs & Services > OAuth consent screen. 2. Complete the branding information (app name, logo, support email, etc.). 3. Submit for verification if required (depends on scopes requested). 4. Set publishing status to 'Production'. ## Acceptance criteria - Any Google user can sign in without being manually added as a test user - No 'This app isn't verified' warning screen appears ## Notes The app only requests basic profile scopes (email, name). This should qualify for a simplified verification process. See: https://support.google.com/cloud/answer/15549049 Google OAuth credentials JSON is saved locally in Downloads/lila/ on the dev laptop.
forgejo-lila added the
infra
 label 2026-04-19 07:23:31 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/adding-spanish
feat/data-feeding
feat/landing-page
feat/navbar
dev
feat/multiplayer-mode
No results found.
Labels
Clear labels   
debt

Technical cleanup, refactoring

  
feature

   
feature

New user-facing functionality

  
infra

Infrastructure, deployment, DevOps

  
multiplayer

   
multiplayer

Multiplayer lobby and game features

  
security

Security improvements

  
ux

User experience, accessibility, polish

No labels
debt
feature
feature
infra
multiplayer
multiplayer
security
ux
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: forgejo-lila/lila#16
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?