UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.33 Safari/537.36

Steps to reproduce the problem:
1. Verify certificate *.foo.com is in mac keychain access
2. Navigate to bar.foo.com in Chrome beta 

What is the expected behavior?
Website loads as "secure" (as indicated in address bar). Communication between site and other sites on *.foo.com allowed.

What went wrong?
Regardless of certificate being trusted in my keychain, I am unable to view the site without receiving a NET::ERR_CERT_COMMON_NAME_INVALID warning.

Clicking through to enable access to the site works does eventually allow me in. The website and the backend API are located as subdomains on *.foo.com and usually, if I access both and trust (if for some reason my certificate is not currently loaded) chrome will happily allow communication between the two. However, after updating I had to bounce back and forth between both sites, reload, and retrust (UI -> trust, API -> trust, UI -> trust) and then it eventually worked.

This was not a problem prior to this update.

Did this work before? Yes Previous version of beta

Chrome version: 58.0.3029.33  Channel: beta
OS Version: OS X 10.12.3
Flash Version: 

Will be checking stable chrome to see if the issue is also there.