HTTP basic auth doesn't work in 2025.10

[suicidaleggroll]

Describe the bug
HTTP basic auth doesn't appear to pass the credentials through to the client in 2025.10. Nothing has changed in my configuration since setting it all up about 6 months ago, everything was working fine through 2025.8, and since upgrading to 2025.10 it has stopped. Navigating to the site with an incognito window prompts for the Authentik username/password, then once that's authenticated it pops up with the HTTP basic auth username/password request instead of proceding silently into the application. I don't see any applicable warnings/errors in the Authentik logs. This applies to every HTTP basic auth app in my network, including the *arrs, selkies-gstreamer, and webtop. All of them stopped working in the same way once upgrading Authentik to 2025.10.

To Reproduce
Follow the steps here to set up the username/password, create a proxy provider in Authentik, check the Use Basic Authentication option and set the username/password to the necessary variables. Then proceed to the site, it still prompts for the HTTP basic auth username/password. These steps worked correctly in 2025.4, 2025.6, and 2025.8, but it no longer appears to work in 2025.10.

Expected behavior
Navigating to https://myapp.mydomain.com should [if necessary] prompt for the Authentik credentials, then once authenticated it should proceed silently into the app, instead of prompting for the Authentik credentials and then the HTTP basic credentials as well.

Screenshots

Version and Deployment (please complete the following information):

• Authentik: 2025.10.0
• Deployment: docker compose

[BeryJu]

this is fixed by #17759 and will be in 2025.10.1

[suicidaleggroll]

Ah thanks, I had searched but I guess not for the right terms