IIS 10 CA Root Certificate is not trusted - ssl

I have successfully installed the SSL and I also installed the Trusted Root Certification in the the Trusted Root Certifications Store.
Yet it is still saying to install it in the trusted root store.
https://www.k-9styles.com/
I am using a Rapid SSL RSA SSL

Related

Tomcat 7 mutual authentication (mTLS)

My situation
I have configured Tomcat for mTLS with self-signed certificates and everything works fine (certificate installed on the browser).
Now I'm trying to configure mTLS for Tomcat with third party certificate provider X and it isn't working.
So,
I have a certificate card and a certificate is issued by a certificate provider X.
I've installed all root certificates of X certificate provider to Tomcat's truststore (public CA storage).
I have self-generated certificate on Tomcat's keystore (server certificate storage)
When I navigate via browser to a webapp I'm not getting prompted to select a certificate which is on my certificate card.
My questions
Do I need to replace self-signed certificate with the one signed by third party certificate provider X for it to work?
Or should installing certificate provider X's CA certificates on Tomcat's truststore should be enough?

How upload my certificate to the Trusted Root Certification Authorities store?

i builded an app running in console with Python. Then i made this app convert to exe. i wanna publish this app on the web. So i signed this app. But i see this problem:
This CA Root certificate is not trusted. Upload this certificate to the Trusted Root Certification Authorities store to be trusted.
From this warning i understand that i must my upload certificate to the Trusted Root Certification Authorities store. But i do not know it way.
My app certificate' s is:
https://www.digicert.com/support/tools/certificate-utility-for-windows
Who issued certificate:
http://127.0.0.1:5000/
Whom was issued certificate:
http://127.0.0.1:5000/
Signature algorithm:
sha256RSA
You're using self-signed certificate i.e. certificate is not issued from valid trusted Certificate Authority. If you want to publish the app for public, then you've to sign it by obtaining the certificate from valid trusted certificate authority (CA). In case, you want to manually share the app with the recipients, and they're aware of the possible risk factor then you can share the issuer certificates with them, and they've installed those into the windows trust store.
Just search for certmgr on windows and add the issuer certificates into Trusted Root Certification.

How to create a Standards Compliant Intermediate SSL Certificate

I have a certificate chain comprised of the root certificate, intermediate certificate, and server certificate. The root certificate is installed on my local machine. The intermediate certificate and server certificate are installed on my tomcat server.
I am unable to find instructions anywhere on how to create an intermediate certificate such that it is standards compliant. This is the error that I am receiving:
Here are the details of the "inter" certificate, according to KeyStore Explorer:

(Internal)CA signed certificate on WebLogic & same CA cert(public key) on my Weblogic Server. Browser still doesn't trust

I have the company CA signed certificate, intermediate and server certificate in the identity store ( .jks) but still the browser says , cannot be verified by a trusted authority error. Using weblogic -10.3.1 from the weblogic logs i also notice this -
Invalid/unknown SSL header was received from peer x.y.z.12 during SSL handshake
But when I install the root and intermediate certificates into certmgr.msc then when i access the url again in a new window it has no error on the browser and also no error log in the weblogic server.
What could be wrong ?
Global CA's have their root and intermediates recognised by all the modern browsers. However when browser encounter s a certificate whose intermediate and roots aka chain certificates & ca certificates are not a part of its trust store so it fails to chain the leaf certificate to its issuer. So in order to mitigate thi, the roots and intermediates of the company ca must be added so that the browser can verify the complete chain.
Agreed .but thats how the trust works. The company issues ca certificate is known only to your organization but browsers are accessed globally and if you want make the certificate trusted in all the browsers then either you switch to public ca issued certificates or get your root certificate cross signed by a global ca root.

Could not establish secure channel for SSL/TLS with authority

I'm having an issue calling an asmx webservice:
Could not establish secure channel for SSL/TLS with authority ...
When I go to the asmx url in a browser on the server (WIN2k12R2 fully patched as of 6 Sep 2016) making the requests I don't see any issue with the certificate. It's issued by COMODO RSA Extended Validation Secure Server CA (Intermediate Certification Authorities), which is issued by COMODO RSA Certification Authority (Intermediate Certification Authorities), which is issued by AddTrust External CA Root (Trusted Root Certification Authorities) - all report ok.
The time on the server (UTC) is synced with 3.europe.pool.ntp.org
I'm using the proxy that was built by Visual Studio.
I've moved the Intermediate COMODO certs to the Trusted Root Certification Authorities and no longer encountered the error - does this seem like a valid solution? It appears to have solved the problem, but I don't understand why.