Skip to Content
Version 2.1 by Mark Kohlmann on 2021/09/10 17:11
Show last authors
1 ==== Why does this happen? ====
2
3 3-series processors with authentication or ssl enabled and all 4-series processors will force all web traffic to use HTTPS.  HTTPS encrypts the traffic using its own certificate.  A normal website will use a certificate that has been signed by a company that is guaranteeing the authenticity of the site.  That guarantee is backed by tracing the signing of the certificate back to root certification authorities using lists that are embedded in all browsers.  If the verification of certificate fails then the certificate is not trusted.  Browsers prompt the user to acknowledge that they know the site has not been validated by a trusted authority.
4
5 ==== What can we do? ====
6
7 There are two solutions to this problem.  One is to establish your own internal trust.  This is typically handled in enterprises as they setup their own root of trust and sign certificates.  It can be done on a smaller scale but it requires knowledge of generating and managing certificates.  The other option is to load the certificate of the processor into the touchpanel as a trusted certificate.  We will not cover setting up your own certificate authority.
8
9 ==== Solving the problem with the processor's certificate ====
10
11 (% class="box warningmessage" %)
12 (((
13 Note, the typical processor certificate expires after a year.  This will need to be done annually.
14 )))
15
16 * Point your computer's web browser to the processor https:~/~/(Processors_IP_Address).  Accept the certificate.
17 * Download the certificate (varies by browser):(((
18 == **INTERNET EXPLORER** ==
19 )))
20 * Navigate to the page that uses the certificate. (Example: For i4Go with iframe, [[HTTPS:~~/~~/i4m.i4go.com>>url:https://i4m.i4go.com/]])
21 * Right-click the page and select **Properties.**
22 * Click **Certificates**.
23 * in the window that opens click the **Details** tab.
24 * Select **Copy to file**. You will be prompted to select an export format. Select the format appropriate for the webserver or interface. If in doubt, the web developer or Interface vendor should be consulted.
25 * (((
26 [[image:https://support.shift4.com/hc/article_attachments/360050763614/mceclip0.png||alt="mceclip0.png" height="415" width="339"]] [[image:https://support.shift4.com/hc/article_attachments/360051673353/mceclip1.png||alt="mceclip1.png" height="415" width="334"]]
27
28 == **FIREFOX** ==
29 )))
30 * Navigate to the page that uses the certificate. (Example: For i4Go with iframe, [[HTTPS:~~/~~/i4m.i4go.com>>url:https://i4m.i4go.com/]])
31 * Right-click and select **View Page Info**
32 * Click the **Security **icon
33 * Click **View Certificates**.
34 * in the window that opens click the **Details** tab.
35 * Click the **Export **Button
36 * (((
37 [[image:https://support.shift4.com/hc/article_attachments/360051673413/mceclip2.png||alt="mceclip2.png" height="313" width="342"]] [[image:https://support.shift4.com/hc/article_attachments/360050763694/mceclip3.png||alt="mceclip3.png" height="376" width="353"]]
38
39 == **GOOGLE CHROME** ==
40 )))
41 * Navigate to the page that uses the certificate. (Example: For i4Go with iframe, [[HTTPS:~~/~~/i4m.i4go.com>>url:https://i4m.i4go.com/]])
42 * Right-click the page and select **Inspect**
43 * Select the **Security **tab.
44 * Click **View Certificate**
45 * in the window that opens click the **Details** tab.
46 * Select **Copy to file**. You will be prompted to select an export format. Select the format appropriate for the webserver or interface. If in doubt, the web developer or Interface vendor should be consulted.
47 * (((
48 [[image:https://support.shift4.com/hc/article_attachments/360051673433/mceclip4.png||alt="mceclip4.png" height="159" width="352"]][[image:https://support.shift4.com/hc/article_attachments/360051673353/mceclip1.png||alt="mceclip1.png" height="415" width="334"]]
49 )))