You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The login of our company's system relies on the certificate of the local computer.
If the certificate cannot be detected, the message "Invalid Certificate Error" will be displayed and the login will fail. According to the document https://docs.cypress.io/guides/references/client-certificates#__docusaurus_skipToContent_fallback, we added client-certificates, but it does not seem to take effect. The Certificate viewer on the Chrome browser opened by Cypress still shows Cypress Proxy CA.
Is there any way to debug whether the client-certificates code is effective?
Desired behavior
The insecure-content label should not be displayed to the left of the URL address bar.
Certificate should be valid instead of invalid
Custom certificate should be displayed on "Certificate Viewer"
User can login correctly. No "Invalid Certificate Error" is displayed when click "SSO" login button
Test code to reproduce
cypress.config.js:
const{ defineConfig }=require("cypress");module.exports=defineConfig({e2e: {setupNodeEvents(on,config){// implement node event listeners hereon('before:browser:launch',(browser={},launchOptions)=>{// `args` is an array of arguments that will be passed to the browser// when it is launchedconsole.log('launchOptions.args:',launchOptions.args)if(browser.name==='chrome'){launchOptions.args.push('--enable-automation');launchOptions.args.push('--ignore-certificate-errors');launchOptions.args.push('--allow-running-insecure-content');launchOptions.args.push('--auto-open-devtools-for-tabs');launchOptions.args.push('--disable-web-security');}returnlaunchOptions;})},"chromeWebSecurity": false,"experimentalModifyObstructiveThirdPartyCode": true,"baseUrl": "https://projectqa.com/","clientCertificates": [{"url": "https://projectqa.com/","ca": [],"certs": [{"pfx": "./cypress/softcerts/astandardu001.pfx","passphrase": "./cypress/softcerts/pfx-passphrase.txt",},],},],},});
E2E:
/// <reference types="cypress" />describe('example to-do app',()=>{beforeEach(()=>{// Cypress starts out with a blank slate for each test// so we must tell it to visit our website with the `cy.visit()` command.// Since we want to visit the same URL at the start of all our tests,// we include it in our beforeEach function so that it runs before each testcy.visit('https://projectqa.pwc.com/')})it('Does not do much!',()=>{expect(true).to.equal(true)})})
Cypress Version
13.13.1
Node version
v18.17.1
Operating System
macOS 13.6.7
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered:
Are the browser launch arguments working as a workaround? I'm not sure why this wouldn't be working. We don't have any current issues opened for clientCertificates not working.
Current behavior
The login of our company's system relies on the certificate of the local computer.
If the certificate cannot be detected, the message "Invalid Certificate Error" will be displayed and the login will fail. According to the document https://docs.cypress.io/guides/references/client-certificates#__docusaurus_skipToContent_fallback, we added client-certificates, but it does not seem to take effect. The Certificate viewer on the Chrome browser opened by Cypress still shows Cypress Proxy CA.
Is there any way to debug whether the client-certificates code is effective?
Desired behavior
Test code to reproduce
cypress.config.js:
E2E:
Cypress Version
13.13.1
Node version
v18.17.1
Operating System
macOS 13.6.7
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: