Organization name is not displayed for a URL which is has a Extended Validation SSL certificate on a Chrome browser on MAC system
Reported by
dharmis...@gmail.com,
Jan 4 2017
|
|||
Issue descriptionChrome Version : <Version 55.0.2883.95b (64 bit)> and lower versions as well such as 54 URLs (if applicable) : https://www.entrust.com, https://thecyberwire.com/, https://cloud.injazat.com, and many more Other browsers tested: Safari:OK version 10.10 (12602.1.50.1.10) Firefox:OK version 50.1.0 IE:OK 11.0 9600.18525 Edge: OK version 20.102.40.17146.0 Chrome on Windows: OK version 55.0.2883.95b 64 bit and 55.0.2883.87 m Chrome on MAC OS: FAIL version 55.0.2883.95b 64 bit and 55.0.2883.87 m What steps will reproduce the problem? (1) Use Google Chrome (version 54 and latest) on MAC or iOS (2)Browse to any of the URL's I have mentioned in Address bar (3)You will see that the organization name is not displayed within the address bar What is the expected result? The organization name should be displayed as compared to other Search engines. What happens instead? The site comes up, however, the organization name is not listed within the address bar. Our Root CA certs are in the MAC OS/iOS Root Trust store as well. Adding one of our competitor’s (Symantec) site which works ok on Windows and MAC with the Chrome browser: https://capitalone.ca (their EV cert may be built differently than ours) I have attached a couple of screenshots to show what happens on a Windows vs a MAC system. Please let us know if you require further information. Best Regards, Dee Patel Product Support Team Lead, Certificate Services Support Entrust Datacard Office: +1 613 270-3707
,
Jan 4 2017
,
Jan 9 2017
Marking WontFix/WorkingAsIntended In Issue 655612 , we aligned the OS X EV treatment with that of other Chrome platforms, by using Chrome's built-in EV metadata rather than the OS's (which itself was an anachronistic decision). Because newer versions of OS X build the chain to the G2 root, these sites were then affected by Issue 442481 , which was the recognition of EV for the G2 root. On the other tested platforms, EV treatment was shown because a path to the non-G2 root is built first, thus resulting in the EV treatment (as the old roots were already enrolled for EV treatment). This issue is resolved as of Chrome 57 / by Issue 442481 , so closing this as a WontFix.
,
Jan 11 2017
Thank you for your reply. We look forward to new release. Dee Patel Entrust Datacard |
|||
►
Sign in to add a comment |
|||
Comment 1 by dharmis...@gmail.com
, Jan 4 2017219 KB
219 KB View Download