Chrome 143 - Forbidden error 403

Pavel Aronovich

unread,

Dec 4, 2025, 9:42:15 AMDec 4

to Chromium Extensions

After updating Chrome to version 143, negotiate authorization on the local server stopped working (NET 9, Windows 11 Pro).

The problem occurs on the browser tab and in the extension. Error: Forbidden 403.

Everything is working on Edge so far.

What could be the problem?

Patrick Kettner

unread,

Dec 4, 2025, 2:10:06 PMDec 4

to Pavel Aronovich, Chromium Extensions

Hi Pavel

Can you elaborate on what you mean by negotiate authorization? Do you mean the SSL cert is failing?

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/6f34eebf-6e55-4715-bc67-79f324a6ebe7n%40chromium.org.

Pavel Aronovich

unread,

Dec 4, 2025, 2:15:05 PMDec 4

to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich

The problem is not ssl, the problem is that the kerberos authorization does not work.

четверг, 4 декабря 2025 г. в 22:10:06 UTC+3, Patrick Kettner:

Patrick Kettner

unread,

Dec 4, 2025, 2:24:14 PMDec 4

to Pavel Aronovich, Chromium Extensions

How are you using Kerberos? I am not aware of an obvious change in 143, but it may be related to the Local Network Access changes that were recently added. Would you possibly be able to try the enterprise policy from that teams migration guide to see if that resolves the 403 error? If it does not, can you please share reproduction steps so I can get to the bottom of it?

thanks!

patrick

Pavel Aronovich

unread,

Dec 4, 2025, 2:44:21 PMDec 4

to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich

I tried LocalNetworkAccessAllowedForUrls it didn't help.

This is a web application with transparent kerberos client authorization on windows. Everything has been working for many years and has not changed. As soon as chrome is updated, authorization issues a 403.

четверг, 4 декабря 2025 г. в 22:24:14 UTC+3, Patrick Kettner:

Patrick Kettner

unread,

Dec 4, 2025, 2:47:01 PMDec 4

to Pavel Aronovich, Chromium Extensions

Ok, then can you please share reproduction steps

Pavel Aronovich

unread,

Dec 4, 2025, 2:52:17 PMDec 4

to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich

If on .NET 9 or 10 for Windows, then the simplest web application with negotiate user authorization. Check that the user is logged in when calling the test http method.

четверг, 4 декабря 2025 г. в 22:47:01 UTC+3, Patrick Kettner:

Patrick Kettner

unread,

Dec 4, 2025, 2:56:00 PMDec 4

to Pavel Aronovich, Chromium Extensions

Without more information, it does not seem to be related to extensions nor do I use kerberos for auth. Without having detailed reproduction steps, this is not something we would be able to help with.

patrick

Pavel Aronovich

unread,

Dec 5, 2025, 6:15:40 AMDec 5

to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich

Here is the application on NET 10 for Windows. It works correctly in Edge, and requires you to enter your username/password in Chrome.

четверг, 4 декабря 2025 г. в 22:56:00 UTC+3, Patrick Kettner:

Negotiate.zip

Patrick Kettner

unread,

Dec 5, 2025, 6:19:57 AMDec 5

to Pavel Aronovich, Chromium Extensions

Hey Pavel

I think it would make sense to file a new bug at crbug.com, as this doesnt seem extension specific.

Pavel Aronovich

unread,

Dec 5, 2025, 11:35:08 AMDec 5

to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich

https://issues.chromium.org/issues/466322593?pli=1

пятница, 5 декабря 2025 г. в 14:19:57 UTC+3, Patrick Kettner:

Reply all

Reply to author

Forward