Hi Guys,
I have just moved back to the world of Mac OS and I am running the latest Big Sur beta. Coming from a Chromebook I really liked using webapps packaged in their own windows. I have an iPhone and iPad and do this with Safari so I was shocked to see that Safari cannot do the same thing for Mac OS. I downloaded Chrome and it works a treat for the few sites that I want as web apps. Except one.
Chrome on Mac OS 11 is showing a certificate error for one particular site, although the same website in Safari shows a valid certificate. I have tried clicking the error and selecting always trust, but it always reverts back to System Default. I then tried dragging the cert to the desktop, renamed the extension to .cert, double clicked it and it seems to have installed it to 'System'. However Chrome still reports an invalid certificate.
I am not overly familiar with the Mac OS Keychain, I haven't regularly used Mac OS in years. I understand the native Chrome cert manager but I guess they're required to use the keychain on Mac OS.
For what it's worth, the same website does not report certificate errors using Chrome on my other devices (iPad, iPhone, Android or Chromebook).
Not sure if this is a Chrome or Big Sur issue. I didn't try the site prior to upgrading to Big Sur. I know, I know, its a beta. But I want the latest and greatest!
It's not the end of the world, I can either use Fluid or just visit it within the browser for now, just wandering if anyone has an ideas as to why two browsers on the same system can't agree on the validity of a certificate when they both appear to use the same keychain certificate library.
Thanks for any suggestions.
I have just moved back to the world of Mac OS and I am running the latest Big Sur beta. Coming from a Chromebook I really liked using webapps packaged in their own windows. I have an iPhone and iPad and do this with Safari so I was shocked to see that Safari cannot do the same thing for Mac OS. I downloaded Chrome and it works a treat for the few sites that I want as web apps. Except one.
Chrome on Mac OS 11 is showing a certificate error for one particular site, although the same website in Safari shows a valid certificate. I have tried clicking the error and selecting always trust, but it always reverts back to System Default. I then tried dragging the cert to the desktop, renamed the extension to .cert, double clicked it and it seems to have installed it to 'System'. However Chrome still reports an invalid certificate.
I am not overly familiar with the Mac OS Keychain, I haven't regularly used Mac OS in years. I understand the native Chrome cert manager but I guess they're required to use the keychain on Mac OS.
For what it's worth, the same website does not report certificate errors using Chrome on my other devices (iPad, iPhone, Android or Chromebook).
Not sure if this is a Chrome or Big Sur issue. I didn't try the site prior to upgrading to Big Sur. I know, I know, its a beta. But I want the latest and greatest!
It's not the end of the world, I can either use Fluid or just visit it within the browser for now, just wandering if anyone has an ideas as to why two browsers on the same system can't agree on the validity of a certificate when they both appear to use the same keychain certificate library.
Thanks for any suggestions.