Step 4 · Create an OAuth client ID

This step issues the identity Kura-chan presents during OAuth — a Client ID and a Client Secret. You’ll paste them into the dashboard in Step 5. About 2 minutes.

The Client Secret is shown only once

The final dialog in this step displays the Client Secret — once. Closing the dialog hides it forever (you can reset it, but never re-see it). Keep this tab open until you’ve completed Step 5.

Why “Desktop app”?

Kura-chan runs as a desktop app on your NAS / Mac / Linux server. In Google Cloud’s OAuth client types, that matches Desktop app.

Benefits of Desktop app:

• Google auto-allows http://localhost:<any port> redirects without manual registration
• Unlike Web application clients, you don’t have to re-register the redirect URI every time

Steps

1. Open the Credentials page

   Left nav → APIs & Services → Credentials, or console.cloud.google.com/apis/credentials directly.

   

2. ”+ Create credentials” → “OAuth client ID”

   Click + CREATE CREDENTIALS at the top → pick OAuth client ID from the dropdown.

   

3. Pick application type “Desktop app”

   • Application type: Desktop app
   • Name: Kura-chan launcher (anything you’ll recognize later)

   

   Do not pick Web application

   Web application requires you to register redirect URIs one by one in the console. That’s outside the scope of this guide — always pick Desktop app.

4. Click “Create”

   The dialog with your credentials appears in a few seconds.

5. Copy the Client ID and Client Secret

   The dialog reads “OAuth client created” and shows two strings: Client ID and Client Secret.

   

   • Client ID looks like 123456789-abcdefghijklmnop.apps.googleusercontent.com
   • Client Secret looks like GOCSPX-xxxxxxxxxxxxxxxxxxxxxxxxx

   Copy both somewhere safe (password manager, or a temporary scratchpad).

   JSON download option

   The right side of the dialog has a “DOWNLOAD JSON” button that saves both credentials as a JSON file. Useful as a backup if you’d rather not store the secret in a password manager.

6. Click OK to close the dialog

   The client appears in the Credentials list. The Client ID is visible later — the Client Secret isn’t.

If you lose the Client Secret

You can reset it:

1. Credentials list → click the OAuth client name
2. Detail page → click ADD SECRET or Reset secret
3. The old secret is invalidated; a new one is issued

Don’t forget to update the dashboard in Step 5 with the new secret.

Common gotchas

"Configure the consent screen first" error

You skipped Step 3. Go back and finish that, then return here.

Next

Have the Client ID and Client Secret copied? Hand them to Kura-chan in Step 5 · Paste the credentials.