sp-dev-fx-webparts: Workbench not working after chrome update - certificate is broken

Category

• Question
• Bug
• Enhancement

Expected or Desired Behavior

Workbench should work properly in chrome, using the dev certificate.

Observed Behavior

Chrome doesn’t trust dev certificate after latest update, showing this error:

Your connection is not private

Attackers might be trying to steal your information from localhost (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID

The reason is, chrome stopped trusting certificate with common name only. to fix this, you will have to build a new certificate and push it as an update to everyone. Currently there is no way to bypass this chrome limitation as far as I checked.

Steps to Reproduce

Update chrome. Try to use the workbench.

Submission Guidelines

Delete this section after reading

• All suggestions or bugs are welcome, please let us know what’s on your mind.
• If you are reporting an issue around any of the samples, please ensure that you have clear reference on the sample and possibly code file, which should be fixed.
• If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and #spfx-tooling on (SharePoint StackExchange)[http://sharepoint.stackexchange.com/]. You can also alternatively submit your question to (SharePoint Developer group)[https://network.office.com/t5/SharePoint-Developer/bd-p/SharePointDev] at Office Network.
• Remember to include sufficient details and context.
• If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.

Thanks for your contribution! Sharing is caring.