Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

API Management: Restrict Gemini API keys

Aperta
#1,239 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Prajna1999 ci sta già lavorando.

Dal 9/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Is your feature request related to a problem?
Starting June 19, 2026, unrestricted API keys for the Gemini API will no longer be accepted, leading to potential unauthorized usage and billing risks. This causes errors and access issues for users relying on this API.

Describe the solution you'd like

  • Restrict existing API keys for the Gemini API in Google Cloud Credentials.
  • Alternatively, generate new restricted keys in Google AI Studio, which are restricted by default.
Original issue

Starting June 19, 2026, the Gemini API will stop accepting requests from unrestricted API keys to prevent unauthorized usage and billing risks. This error shows up

[GOOGLE_GCP] Authentication / permission denied (code: 403 PERMISSION_DENIED): Lightning dunning decision is deny for project: projects/877240188032. Verify the Google GCP API key is valid and not expired, the project_id and location are correct, and the service account has access to the requested model.

If your Google Cloud project has the Gemini API enabled and contains unrestricted keys, please restrict them immediately.
What to do:

Option 1 (Restrict existing keys): Go to [Google Cloud Credentials](https://console.cloud.google.com/apis/credentials), select your key, and under API restrictions, restrict it to Gemini API ([generativelanguage.googleapis.com](http://generativelanguage.googleapis.com/)).
Option 2 (New keys): Generate new restricted keys in [Google AI Studio](https://aistudio.google.com/app/apikey) and update your code.

Note: Keys generated directly in AI Studio are restricted to the Gemini API by default.

Lingua principale
Python
Stelle
18
Fork
11
Merge medio
3g 2h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ProjectTech4DevAI/kaapi-backend

Tutte le issue di ProjectTech4DevAI/kaapi-backend

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.