Why This Happens:
The “Not Secure” message appears because the site certificate doesn’t meet the latest security standards. Chrome, unlike Internet Explorer, treats it as invalid. From Chrome 58 onwards, only the subjectAlternativeName extension is used to match the domain name and site certificate, not the commonName. A registry fix was available but only worked up to version 65. More details can be found here.
How to Fix It:
You need to issue a new self-signed certificate for *.cloud.onebox.dynamics.com and update the website binding settings to use it.
Step 1: Create a New Self-Signed Certificate Run the following PowerShell command as an administrator:
New-SelfSignedCertificate -Subject "CN=*.cloud.onebox.dynamics.com,O=Microsoft Corporation,L=Redmond,S=WA,C=US" -DnsName "*.cloud.onebox.dynamics.com", "usnconeboxax1ecom.cloud.onebox.dynamics.com", "usnconeboxax1pos.cloud.onebox.dynamics.com", "usnconeboxax1ret.cloud.onebox.dynamics.com" -CertStoreLocation "cert:\LocalMachine\My" -KeyUsage DataEncipherment, KeyEncipherment, DigitalSignature -HashAlgorithm "SHA384" -KeyAlgorithm RSA -KeyLength 2048 -NotAfter (Get-Date).AddYears(5)
This command creates a new certificate that expires in 5 years. You can also use a free Self-Signed Certificate Generator for this purpose.
Step 2: Copy the New Certificate to Trusted Certificates Folder Open “Manage computer certificates” (certlm). Find the new certificate in the Personal\Certificates folder. It will have the same name as the old one but with a different expiration date. Copy and paste the new certificate into the Trusted Root Certification Authorities\Certificates folder.
Step 3: Bind the New Certificate with D365FO
- Open Internet Information Services (IIS) Manager.
- Navigate to the
AOSServicesite. - Click the
Bindingslink on the right. - Select the host name and click the
Editbutton. - In the
Edit Site Bindingdialog, open the SSL certificate drop-down selection box. - Select the new certificate (check the expiration date to confirm).
If prompted, confirm the change for other related sites as well.
Close all dialogs and restart the AOSService by clicking the Restart link under Manage Websites.
Step 4: Test the Connection Restart Chrome and navigate to D365FO. The connection should now be secure.
Comments
Post a Comment