1
I’d like to point out that I’m new to the IIS, so I apologize for the layman and amateur aspect. Well the problem is this, I created a self-signed certificate with the following user-friendly name : "*.site.com" clicked OK and it was associated with the web server. Then I went to Binding with the site, the link editing screen looked like this:
Screen of site links https://i.stack.Imgur.com/M97wq.png
Opening the browser I find that the certificate I created made this link to the site, but returns me a status of : "NOT SAFE" I am using the Drive API in the application for handling files in Drive, the login in Oauth is not even working anymore, certainly due to this.
I’m having two mistakes:
When I check the browser security tab, the first one is SAN (Subject Alternative name ) which apparently reports that a package containing an alternate name was not created in the certificate. When I create a self-serving certificate it just demands a friendly name, and that’s all, correct ?
And that alternate name needs to be a match with the domain name I define on the site’s link screen ?
And the second error is related to "common name invalid".
Mistakes : https://i.stack.Imgur.com/72oqv.png
I need a north for the solution of this problem. Already, I thank.