CODEWITHSUNDEEP
electron
Lonnie Best
Lonnie Best

Reputation: 11399

Overriding Self-Signed SSL Certificate Warnings with Electron

There are two prior questions leading to this question (if you're interested):

  1. ssl-for-intranet-applications-deployed-at-multiple-companies
  2. distributing-ssl-certificates-to-all-browsers-in-an-active-directory-environment

In Electron, do you have the ability to override SSL certificate warnings that you'd typically get when using self-signed certificates via a modern web browser?

Typically, in desktop applications, you do not have to adhere to the strict online-banking-level certificate standards that web browsers warn about. The data I'm transferring isn't that sensitive.

As a matter of fact, one of the only reasons I'm moved my app from http to https, is because certain web standard APIs won't function unless the protocol is https. The Notification API is one example.

Otherwise, the data I'm transferring over intranet just isn't that sensitive. Yet, the browsers attempts to burden me (and my users) with Online-Banking-Level certificate authentication.

I'm trying to avoid this somehow and thought that maybe Electron could give me more client-side control for pre-approving my self-signed certificate. Is this doable in Electron?

Upvotes: 0

Views: 1509

Answers (1)

Andreas Dolk
Andreas Dolk

Reputation: 114787

I have some trouble with https and untrusted proxy certificates and this in my index.js

// We have to deal with self-signed and therefore untrusted root certificates.
global.process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0';

It's an intranet application that never reaches out to the internet, so it's ok for me here.

Upvotes: 2

Related Questions