Wrong common name? about getssl

[githubRover]

Let's Encrypt made a recent change about the CN Name. Read more about that here:
https://community.letsencrypt.org/t/domain-ordering-not-respected-unexpected-certificate-subject/195337/23

Also see this for general info about CN Name. It's written by a dev for a different ACME Client but the notes regarding Let's Encrypt behavior is the same for all ACME clients.
certbot/certbot#9633 (comment)

[exxosuk]

Thanks, so this should really solve itself then.

[githubRover]

Well, it depends on what you were expecting in the CN Name field. From the post by jsha:

Update: We've decided to go back to the old behavior: issuance requests with no Subject CN in the CSR will have the first SAN copied into the Subject CN of the issued certificate

[exxosuk]

The first SAN would solve my problem. Oddly seems to be choosing the last one in the list currently.

Though I cannot figure out if this can be set manually or not. It sounds like it was phased out. It's a bit confusing.

[githubRover]

In long term CN name will be empty (no timeframe). It was deprecated like 20+ years ago and the industry looks for ways to shrink the certs that traffic the net.

If you are building something new which looks at CN name you might consider an alternative approach.