Repository navigation
[Feature] Support of multiple HTTP credentials for different origins #22013
Description
With feature #20464 it is possible to specify the origin of http credentials.
An idea of enhancement would be to allow providing multiple credentials for different origins.
For example if different username/password are needed on either server1.com or server2.com, we could specify an array of httpCredentials (username/password/origin):
await browser.newContext({httpCredentials: [
{ username: 'user1', password: 'pass1', origin: 'https://server1.com' },
{ username: 'user2', password: 'pass2', origin: 'https://server2.com' }
]);
To be discussed:
- backward compatibility creating context with non array httpCredentials
- new naming for array httpCredentials
- edge case when 1 httpCredentials does not have origin (what credentials to use for server.com ?):
await browser.newContext({httpCredentials: [
{ username: 'user1', password: 'pass1' },
{ username: 'user2', password: 'pass2', origin: 'https://server.com' }
]);
- edge case when 2 httpCredentials do not have origin (what credentials to use for server.com ?):
await browser.newContext({httpCredentials: [
{ username: 'user1', password: 'pass1' },
{ username: 'user2', password: 'pass2' }
]);
- edge case when 2 httpCredentials have the same origin (what credentials to use for server.com ?):
await browser.newContext({httpCredentials: [
{ username: 'user1', password: 'pass1', origin: 'https://server.com' },
{ username: 'user2', password: 'pass2', origin: 'https://server.com' }
]);
Reacted by tokyo-watcher, Gianmarco Doro, Anderson, Takumi Kaji, kuanhung.chen, George Palfreyman, Yuki Mima, Kaoru Shirai, ediezindell and Sébastien Richert
Activity
SebastienRichert commentedon Mar 28, 2023
Regarding the edge case
3.,4.,5., question is whether we should:3.uses user1/pass14.uses user1/pass15.uses user1/pass1tokyo-watcher commentedon Sep 6, 2023
pavelfeldman commentedon Aug 16, 2024
Why was this issue closed?
Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.
If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.
Gby56 commentedon Jul 16, 2026
Hello Pavel Feldman (@pavelfeldman) , I saw this issue and encountered the same problem. I can try to make a PR for this
Gby56 commentedon Jul 16, 2026
Hi Dmitry Gozman (@dgozman) ! I use playwright for browser automation, people provide to us authentication details, sometimes we must crawl/review multiple web applications that use different auths, but we must use the same playwright context (weird, I know)
Apparently Chromium/Firefox allow for multiple auths setup, Webkit doesn't, that's the main difference. I would like to use the native playwright feature instead of putting a proxy in front to handle all of this, since browsers do it very well.