In case a client certificate is required to connect to the site to be tested during a MagicPod browser test, the client certificate can be automatically selected according to preconfigured settings.
Support target
Execution environment
Currently, this only supports Chrome in the Cloud environment or Chrome for local PC environment (Mac only).
- There are no plans to support external Cloud services (SauceLabs, BrowserStack).
- Although there are no current plans to support other local PC environments (Windows PC Chrome or other browsers), consult with support if necessary. We shall consider whether to provide support.
Types of certificate files
This only supports PKCS #12 type (with .pfx or .p12 extension).
Reference: Certificate file types
Since MagicPod 1.0.0, certificate files with old cipher algorithms (like RC2, RC4, RC5, DES, MD2, MD4, MDC2, RMD160, CAST5, Blowfish, IDEA, SEED) cannot be uploaded. Please use newer algorithms to upload new files. You can keep using already uploaded files regardless of the cipher algorithm.
Setup method (Cloud)
Open the test run settings panel and set the Environment option to Cloud.
When you open the Advanced settings tab, you will find the Client certificates settings item.
For Cloud environments, the certificate(s) used for the test must be uploaded to the MagicPod Server.
When you click the Manage certificates button, the dialog box for registration will be displayed, so register the file.
After selecting the file, enter the password for the certificate file. This password is required to install the certificate on the machine for running the test on the Cloud.
After completing registration, click the Close button to return to the test run settings panel.
After closing the dialog box, select the certificate you have just registered in the pull-down menu for selecting certificates. Alternatively, enter part of the URL for the site where you wish to use this certificate in the column where Enter URL pattern is written.
As the URL pattern will be a partial match, you can specify as in the figure above when you are accessing a URL such as “https://test.example.com/login”.
This completes the settings. If you run the test in this state, the client certificate will be automatically selected during execution.
Setup method (Local PC)
If you are using a client certificate for a local PC test on Mac, install the certificate on the PC in advance.
Open the test run settings panel and set the Environment option to Local PC.
When you open the Advanced settings tab, you will find the Client certificates settings item.
Unlike in the Cloud, there is no need to store the certificate on the Server, but you will need to enter the issuer name of the certificate instead. If you do not know the issuer name, you can look it up using the following procedure. (From the second use onward, if you already know the issuer name, you can skip the following steps.)
If you click the Get issuer name button, the following dialog box will be displayed, so upload the certificate file according to the instructions and enter your password. The password you enter here is the same password as when you installed the certificate on the local PC. This is necessary for analyzing the certificate and acquiring the issuer name. The certificate itself is uploaded to the Server once and analyzed, but as it is not required after that point, it will not be stored on the Server.
Once the analysis completes, the following message will be displayed.
The analyzed issuer name is stored on the clipboard, so enter this by pasting it into the Enter issuer name column. Alternatively, enter part of the URL for the site where you wish to use this certificate in the column where Enter URL pattern is written.
As the URL pattern will be a partial match, you can specify as in the figure above when you are accessing a URL such as “https://test.example.com/login”.
This completes the settings. If you run the test in this state, the client certificate will be automatically selected during execution.