Skip to content

Panther fails on Curl certificate validation on readiness trait #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
benrcole opened this issue May 2, 2020 · 2 comments · Fixed by #456
Closed

Panther fails on Curl certificate validation on readiness trait #335

benrcole opened this issue May 2, 2020 · 2 comments · Fixed by #456

Comments

@benrcole
Copy link

benrcole commented May 2, 2020

Hi

It doesn't seem possible to use Panther without valid ssl certs. Whilst the environment variable switch can tell chrome to ignore certificate errors, WebServerReadinessTrait::waitUntilReady generates a curl client that is fails due to invalid certificates.

Switching out

$client = HttpClient::create(['timeout' => $timeout]);

for

$client = HttpClient::create(['timeout' => $timeout, 'verify_host' => false, 'verify_peer' => false]);

enables me to test with Panther but this doesn't seem achievable via config, or am I missing something?

Ben

@wickedOne
Copy link
Contributor

wickedOne commented Oct 3, 2020

hi ben,

now that this pr is merged, you can pass additional capabilities to the panther client like this:

$client = static::createPantherClient(
  [
    'external_base_uri' => 'https://my.site.test',
    'browser' => 'firefox',
  ], 
  [],
  [
    'capabilities' => [
        'acceptInsecureCerts' => true,
    ],
  ]
);

@pscheit
Copy link

pscheit commented Apr 6, 2025

acceptInsecureCerts didnt work for me but:

            managerOptions: [
                'host' => 'http://selenium:4444/wd/hub',
                'capabilities' => DesiredCapabilities::chrome()
                    ->setCapability(WebDriverCapabilityType::ACCEPT_SSL_CERTS, true)
                ,
            ],

did

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants