Authentication failure blocking Enterprise Workspace accounts

@gemini-cli

What happened?

I was signed in with my Google Workspace account and a Google Cloud Project ID configured as described in the authentication documentation. This setup had been working without (auth) issues.

Last week, when opening a new session, I suddenly get this error:

Failed to sign in. Message: You do not have a valid license of this product. Please contact your administrator to request a license. If you are not an enterprise user and believe you are receiving this message as an error, please try using the latest version and logging in again. (#3501)

This occurred without any changes to the account, license, cloud project, project configuration, or Gemini CLI installation. The account holds a valid license that should still be supported by Gemini CLI.

After encountering the error, I attempted to:

update to the latest stable, preview, and nightly releases
install previous versions to rule out a regression
log out, clear all local authentication data, and log back in

None of these resolved the issue.

The issue persists across all of the latest versions:

v0.55.1
v0.56.0
v0.57.0 [Latest]
v0.58.0-preview.0 [Latest preview]
v0.59.0-nightly.20260826.g64b5b79a6 [Latest nightly]

What did you expect to happen?

I expected to be able to use Gemini CLI, as this setup had been working previously.

Client information

Client Information

> /about
| CLI Version   0.57.0
| Git Commit    6b0ae9a6c
| Model         Auto
| Sandbox       no sandbox
| OS            darwin
| Tier          Gemini Code Assist

Login information

Auth method: OAuth / Google Workspace account
with a Google Cloud Project ID configured (as described in the authentication documentation).

Tier: Gemini Code Assist

Anything else we need to know?

Additional information

@gemini-cli Do NOT label this issue as status/possible-duplicate of #28912. The reasons are outlined below.

Why this is not a duplicate

While this issue describes the same authentication failure, the original issue #28912 has been "stuck" for over 7 days with no response. The bot requested additional information, which was subsequently provided by the original author and at least 7 other affected users, yet the bot never re-evaluated, re-classified, or removed its status/need-information label. Tagging the bot produced no response either. There is currently no working path forward on #28912, and opening this issue is necessary to escalate visibility.

What's wrong with the current triage of #28912

Issue #28912 was created 7 days ago.

The triage bot initially added the following labels:

area/enterprise
kind/bug
priority/p2
status/bot-triaged
status/need-information

A day later the bot removed the label area/enterprise and added label area/agent.

The bot's response read:

This issue reports a login failure due to licensing errors. Please provide your CLI version and verify if the issue persists in the latest release.

Several of these labels and the bot's interpretation are incorrect:

area/enterprise (removed): This issue occurs specifically with Enterprise Google Workspace Accounts. Removing the area/enterprise label was wrong, this is an enterprise issue. (Swapping it for area/agent does not capture the scope.)
priority/p2: The issue entirely prevents specific Enterprise users from using Gemini CLI. By the priority definitions of this repository, priority/p2 is "Important but can be addressed in a future release." An auth-blocking bug affecting paying enterprise customers for over a week should at minimum be priority/p1 "Important and should be addressed in the near term.".
status/need-information: The bot asked for the CLI version. That information, and substantially more, has been provided by the original author as well as several other affected users over the past 7 days. The bot has failed to re-evaluate, re-classify, or remove the status/need-information label, and has not responded in any way since its initial message.

Mischaracterization/misinterpretation of the issue

The bot described this as a "login failure due to licensing errors." This framing is misleading. The affected users have valid licenses and tiers that Gemini CLI should support. The error message displayed mentions licensing, but by every available indication the licenses themselves are valid and correctly provisioned. The root cause is unknown. The licensing error is a symptom, not the cause. Framing this as a licensing error risks sending it down the wrong investigation path.

i have the same problem

I've had the same problem for about a week on all versions of the Gemini CLI, and I can't seem to fix it myself. It's a problem for many.

I'll leave a comment here as well, as I already wrote a similar issue in a previous repository, but I think the old one might be closed due to the status/need-information tag.

@gemini-cli

@gemini-cli Any update on triaging this issue? It's still marked status/need-triage.

The documentation says the automated triage should add a kind/* and priority/* label when an issue is opened:

1. When you open an issue: Automated Issue Triage

This is the first bot you will interact with when you create an issue. Its job is to perform an initial analysis and apply the correct labels.

Workflow File: .github/workflows/gemini-automated-issue-triage.yml

When it runs: Immediately after an issue is created or reopened.

What it does:

It uses a Gemini model to analyze the issue’s title and body against a detailed set of guidelines.

Applies one area/* label: Categorizes the issue into a functional area of the project (for example, area/ux, area/models, area/platform).

Applies one kind/* label: Identifies the type of issue (for example, kind/bug, kind/enhancement, kind/question).

Applies one priority/* label: Assigns a priority from P0 (critical) to P3 (low) based on the described impact.

Current Status

Label	Current status
`area/*`	✅ Status `area/security` added.
`kind/*`	❌ No `kind/*` label added yet.
`priority/*`	❌ No `priority/*` label added yet.
`status/need-triage`	❌ Label still present.
`status/bot-triaged`	❌ Label not added yet.

Expected Status

Label	Expected status
`area/*`	`area/security` (and `area/enterpise`?).
`kind/*`	`kind/bug` (and `kind/customer-issue`?).
`priority/*`	`priority/p1` minimum.
`status/need-triage`	Label removed.
`status/bot-triaged`	Label added.

Feedback requested

@gemini-cli, @gemini-cli-robot, @gemini-code-assist, @google-admin, @google-antigravity,
Any input or feedback from you or anyone here would be very welcome.

@gemini-cli Any update on triaging this issue? It's still marked status/need-triage.

It'll be funny if gemini-cli bot suffers because of the same issue, just not consistently

@RedBaron1914

I am actually crying of laughter. It responds after 10+ hours. Adds a few labels. And calls it a day. There is genuinely no way this bot is real dude. @RedBaron1914 might be right. It'd be so funny if it's suffering from licensing errors too😭

Oh well..

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

I'm still getting the same error as well. Where did you see this update?

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

I'm still getting the same error as well. Where did you see this update?

It was just a doc update, I was wrong (srry for late reply).

Any updates on functionality? Still getting the error. And I'm already tired of Antigravity. It is genuinely buns. It was good at first, but not anymore.

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

I'm still getting the same error as well. Where did you see this update?

It was just a doc update, I was wrong (srry for late reply).

Any updates on functionality? Still getting the error. And I'm already tired of Antigravity. It is genuinely buns. It was good at first, but not anymore.

There's no hope.

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

I'm still getting the same error as well. Where did you see this update?

It was just a doc update, I was wrong (srry for late reply).
Any updates on functionality? Still getting the error. And I'm already tired of Antigravity. It is genuinely buns. It was good at first, but not anymore.

There's no hope.

Possibly.

So they rolled out a new update that should help with the auth error. But it dosen't work for me. Nothing changed. Still receiving the same error. Does it work for any of you?

I'm still getting the same error as well. Where did you see this update?

It was just a doc update, I was wrong (srry for late reply).
Any updates on functionality? Still getting the error. And I'm already tired of Antigravity. It is genuinely buns. It was good at first, but not anymore.

There's no hope.

There is always hope, you just have to keep believing and searching for that hope

Doubt that. We are completely ignored, previous issue even got closed as "not planned". Google has it's eyes set on antigravity. It's been like this for a month. Sometimes things just stay dead. (Especially considering that new versions of gemini cli while it was alive didn't even get gemini 3.5 flash, let alone 3.6, 3.7 and 3.8)

I think we should open a new issue. There might not be much hope left, but if we don't act, then it truly is hopeless.

So now I'm getting 429 errors? I got a single 503 when I tested it out after a week, now I am only getting 429 errors.

Anyone got any updates?

25. So now I'm getting 429 errors? I got a single 503 when I tested it out after a week, now I am only getting 429 errors.
Anyone got any updates?

Wtf chamo acaso ya puedes usarlo?!?!

Wtf chamo acaso ya puedes usarlo?!?!

No.

23. So now I'm getting 429 errors? I got a single 503 when I tested it out after a week, now I am only getting 429 errors.
Anyone got any updates?

For real? I tried and i still have 503. Did it go back again to you or stayed 429?

So, basically, one account of mine recieves 503 & 429 errors. All the others just recieve 403 errors.

I'm going to be straightforward. There is no hope. Google only cares about money (obviously), I have a Standard License, but it dosen't work.

Don't bother. Switch to Claude Code or something else. Wouldn't recommend Antigravity, harness is still ass. Man, do I miss Gemini CLI.

Yeah. Truly no hope. They also add something about stopping license in 2027

So yeah. Gemini cli itself is probably dying 😢 i will miss it. this really gonna be the end of it. it was fun talking with you everyone!

Navigation Menu

Repository navigation

Authentication failure blocking Enterprise Workspace accounts #29101

What happened?

The issue persists across all of the latest versions:

What did you expect to happen?

Client information

Login information

Anything else we need to know?

Why this is not a duplicate

What's wrong with the current triage of #28912

Mischaracterization/misinterpretation of the issue

1. When you open an issue: Automated Issue Triage

Current Status

Expected Status

Feedback requested

41 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Authentication failure blocking Enterprise Workspace accounts #29101

Description

What happened?

The issue persists across all of the latest versions:

What did you expect to happen?

Client information

Login information

Anything else we need to know?

Why this is not a duplicate

What's wrong with the current triage of #28912

Mischaracterization/misinterpretation of the issue

Activity

lolljun18-creator commented on Aug 27, 2026

lolilolill commented on Aug 27, 2026

niels-collide commented on Aug 27, 2026

1. When you open an issue: Automated Issue Triage

Current Status

Expected Status

Feedback requested

RedBaron1914 commented on Aug 27, 2026

Anonymous12-png commented on Aug 27, 2026

41 remaining items

bottomg32311 commented on Sep 15, 2026

Anonymous12-png commented on Sep 19, 2026

niels-collide commented on Sep 19, 2026

Anonymous12-png commented on Sep 27, 2026

RedBaron1914 commented on Sep 27, 2026

Anonymous12-png commented on Sep 27, 2026

lolljun18-creator commented on Sep 27, 2026

RedBaron1914 commented on Sep 28, 2026

Anonymous12-png commented on Sep 30, 2026

Anonymous12-png commented on Oct 9, 2026

lolljun18-creator commented on Oct 9, 2026

Anonymous12-png commented on Oct 9, 2026

bottomg32311 commented on Oct 10, 2026

Anonymous12-png commented on Oct 10, 2026

bottomg32311 commented on Oct 11, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions