Previous
After installing the device certificate in the machine, enable the SSL/TLS setting.
This procedure is used for a self-signed certificate or a certificate issued by a certificate authority.
Log in as the network administrator from Web Image Monitor.
Point to [Device Management], and then click [Configuration].
Click [SSL/TLS] under "Security".
For IPv4 and IPv6, select "Active" if you want to enable SSL/TLS.
Select the encryption communication mode for "Permit SSL/TLS Communication".
If you want to disable a protocol, click [Inactive] next to "TLS1.2", "TLS1.1", "TLS1.0", or "SSL3.0".
At least one of these protocols must be enabled.
Under "Encryption Strength Setting", specify the strength of encryption to be applied for "AES", "3DES", and/or "RC4". You must select at least one check box.
Note that the availability of encryption strengths will vary depending on the settings you have specified for "TLS1.2", "TLS1.1", "TLS1.0", or "SSL3.0".
Click [OK].
“Updating...” appears. Wait for about one or two minutes, and then click [OK].
If the previous screen does not appear again after you click [OK], wait for a while, and then click the web browser's refresh button.
Log out.
If you set "Permit SSL/TLS Communication" to [Ciphertext Only], communication will not be possible if you select a protocol that does not support a Web browser, or specify an encryption strength setting only. If this is the case, enable communication by setting [Permit SSL / TLS Communication] to [Ciphertext / Cleartext] using the machine's control panel, and then specify the correct protocol and encryption strength.
The SSL/TLS version and encryption strength settings can be changed, even under [Network Security].
Depending on the states you specify for "TLS1.2", "TLS1.1", "TLS1.0", and "SSL3.0", the machine might not be able to connect to an external LDAP server.
If only TLS1.2 and TLS1.1 are enabled, Integration Server authentication cannot be performed.
The following types of communication and data are always encrypted by SSL3.0: communication via @Remote, Integration Server authentication, files sent via a delivery server, and logs transferred to Remote Communication Gate S.
