Google 59不再支持嵌入式凭据 [英] Google 59 no longer supports embedded credentials

问题描述

我是具有一些JS知识的QA分析师，并且正在使用Selenium Webdriverjs进行自动化。该站点需要用户名/密码，因此它是使用嵌入式凭据进行设计登录的（ https：// user：password @ address.com ）。但是，随着本周最近对Chrome 59的更新，即使配置发生变化，也不再允许此功能。有没有人知道如何处理当您到达需要它的网站时出现的身份验证框？我曾尝试将其视为警示框，并且不相信它是模态窗口。任何帮助将不胜感激。

I am a QA analyst with some JS knowledge and am using Selenium Webdriverjs for some automation. The site requires username/password, so it was designed using the embedded credentials to login (https://user:[e-mail]). However, with the recent update to Chrome 59 this week, this ability is no longer allowed, even as a configuration change. Does anyone know how to handle the authentication box that appears when you reach a site that requires it? I have tried treating it as an alert box and do not believe it is a modal window. Any help would be greatly appreciated.

推荐答案

SO用户提到了一个很好的黑客 zoonabar 在此 SO post 。如果您使用有效凭据命中资源/ URL，则在实际访问需要凭据的URL之前，浏览器会缓存身份验证，然后您可以使用它。请看他的回答。

There is a nice hack mentioned by a SO user zoonabar in this SO post. If you hit a resource/URL with valid credentials , before actually hitting the URL that needs credentials, then browser caches the authentication and then you can use it. Please see his answer.

这里也讨论了这个问题 - SO发布关于基本身份验证。

This has also been discussed here - SO Post about Basic Authentication.

另一种选择是运行透明代理来注入标头所需的凭证 - 由Florent B在上述同一链接中提到。

Another option is to run a transparent proxy to inject the header with the required credentials- mentioned by Florent B in the same link mentioned above.

在我们的案例中，选项1（由zoonabar制定）计算出来。你也可以试试他的黑客。

In our case, Option 1 (by zoonabar) worked out. You can also try his hack.

这篇关于Google 59不再支持嵌入式凭据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！