Prerequisites for installing SCC

Before installing Samsung Cloud Connector (SCC), you must satisfy the following prerequisites in your network, server, and Knox Manage tenant.

Prepare your services, server, and network

License

Set up your Knox Manage tenant and register your Knox Manage license.

OS requirements

SCC is compatible with the following operating systems:

• Microsoft Windows Server 2008 R2 (64-bit)
• Microsoft Windows Server 2012 (64-bit)
• Microsoft Windows Server 2016 (64-bit)
• Microsoft Windows Server 2019 (64-bit)
• Windows Server 2022 (64-bit)

JDK requirements

Your SCC client server requires the Java Development Kit (JDK) in the following configuration:

• JDK 1.8.0 (64-bit)
• Patch the JCE module based on the JDK version. For more information, see Install Java patches.

Recommended JDK versions

We recommend using a JDK version from the following list, as these versions have been formally tested for the SCC client.

Install JDK patches

To install the Java Cryptography Extension (JCE) and support TLS v1.2 AES 256:

1. Download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files that match the JDK version. For more information, visit the Oracle website.

   If you have a higher JDK version such as 1.8.0_151-b12, you don’t need a JCE patch. Skip to step 5.

2. Decompress the downloaded file. A sub-folder named UnlimitedJCEPolicy is created.

3. Check if the following files are included in the folder:

   • README.txt
   • local_policy.jar — Unlimited strength local policy file
   • US_export_policy.jar — Unlimited strength US export policy file

4. Copy the two JAR files (local_policy.jar and US_export_policy.jar) to the %JAVA_HOME%\jre\lib\security folder.

5. For JDK versions with the following targets, configure the security setting for the crypto policy:

   Target version

   • Oracle OpenJDK — 1.8.0_181, 1.8.0_251, 1.8.0_291, 1.8.0_311, 1.8.0_341
   • Azul Zulu Prime — 1.8.0_181, 1.8.0_252, 1.8.0_292, 1.8.0_312, 1.8.0_345

   Configuration

   Add (or remove annotation) crypto.policy=unlimited in the java.security file in the %JAVA_HOME%\jre\lib\security folder.

Firewall exceptions

• The firewall between the SCC client and the LDAP server should be open.
• The firewall between the SCC client and the CA server should be open.
• The firewall between the L4 switch for accessing the SCC server and the SCC client. Refer to the list below for the firewall information of L4 domains according to the service regions.

Aside from region code 01, if the region code is between 02 and 07, then you must include the region code after the area name (ap, us, eu) of the firewall domain. Your region code can be found in the URL of your Knox Manage console session.

TCP communication resources

The SCC server and SCC client are connected through TCP communication. To enhance the TCP performance of the SCC client, you must change the registry value.

Set up the TCP communication resource

We recommend changing the registry value for the TCP resource in the SCC client for enhanced TCP performance.

To change the registry value, complete the following steps:

1. On your computer, open the Registry Editor.

2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

3. Change the value each of the following items. If the value does not exist, right-click anywhere on the screen, and then select New > DWORD (32- bit) Value to create a new one.

   • TcpTimedWaitDelay — Change the default value from 240 (4 minutes) to 30 (30 seconds) to convert the disconnected TCP resource rapidly. For more information, see https://technet.microsoft.com/enus/library/cc938217.aspx.
   • MaxUserPort — Change the default value from 5000 to the maximum value of 65534 to increase the number of concurrent requests delivered to SCC from the application. For more information, see MaxUserPort in the Microsoft docs.

Check open source license information

To check open source license information for SCC, refer to the following file on the folder where the SCC client is installed:

{SCC installation location}\scc-client\resources\SCCClient-OpenSourceLicense.xml

Copy the secret token

You can enter a secret token while installing the SCC client. The added security the secret token provides helps authorize SCC, and prevents data leaks through the KM-SCC-LDAP channel.

To copy the secret token:

1. Go to Setting > Configuration > Basic Configuration in the Knox Manage console.

2. Click the Cloud Connector tab, then click Copy.