Overview:
For HSTS (HTTP Strict-Transport-Security), some of the moderm browser(s) like Chrome and Edge will reject a https web site with a self-signed certificate. It will show NET::ERR_CERT_COMMON_NAME_INVALID and do not allow you to browse it.
Purpose:
This article will show workaround.
Target Audience:
For those engineer(s) whom want to use the Chrome or Edge browser to navigate the redfish API. The TA should have the knowledge about the DMTF / redfish API and use Chrome or Edge browser.
Pre-requirement:
1. A DNS record with one domain name mapping to the IP address of the BMC.
2. One server with BMC which support redfish API support https.
3. A working computer with Chrome or Edge browser.
4. Make sure your working computer can access the BMC.
Procedures:
1. Open the Chrome or Edge browser.
2. Enter https://<domain name of the BMC>/redfish/v1
3. The browser will show an error like NET::ERR_CERT_COMMON_NAME_INVALID
4. Click anywhere within the browser window and type: thisisunsafe
5. You will see the formal response without any error if everything are correct.
--- End of this article ---
Comments
0 comments
Please sign in to leave a comment.