Customizing the SSL Network Extender Portal

You can modify the SSL Network Extender Portal by changing skins and languages.

Configuring the Skins Option

To configure the Skins Option:

The skin directory is located inside the $FWDIR/conf/extender directory on the Security Gateways.

There are two subdirectories:

  • chkp: contains skins that Check Point provides by default. During upgrade, this subdirectory may be overwritten.

  • custom: contains skins defined by the customer. If this subdirectory does not exist yet, create it. During upgrade, this subdirectory is not overwritten. New skins are added in this subdirectory.

Disabling a Skin

  1. Enter the specific skin subdirectory, in the custom directory that is to be disabled, and create a file named disable. This file may be empty.

  2. If the specific skin does not exist in the custom directory, create it and then create a file within it named disable.

  3. Install Policy.

    The next time that the user connects to the SSL Network Extender portal, this skin is not available.

Example

cd $FWDIR/conf/extender/skin/custom

mkdir skin1

touch disable

Creating a Skin

  1. Enter the custom subdirectory.

  2. Create a directory with the applicable skin name.

    Note - Make sure this name is not already used in chkp. If it is, the new skin definition overrides the existing skin definition (as long as the new skin definition exists). Once you have deleted the new skin definition, the chkp skin definition is used again.

    Each skin folder must contain these CSS files:

    • help_data.css - The main OLH page uses this stylesheet.

    • help.css - The inner frame on the OLH page uses this stylesheet.

    • index.css - The ESOD pages, and the main SSL Network Extender portal page use this stylesheet.

    • style.css - All login pages use this stylesheet.

    • style_main.css - The main SSL Network Extender Connection page, Proxy Authentication page, and Certificate Registration page use this stylesheet.

    Best Practice - We recommend that you copy these files from another chkp skin, and then modify them as applicable.

  3. In SmartConsoleClosed Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on., install policy.

Example

Add your company logo to the main SSL Network Extender portal page.

  1. cd $FWDIR/conf/extender/skin/custom

  2. mkdir <skin_name>

  3. cd <skin_name>

  4. cp -v../../chkp/skin2/* .

  5. Place logo image file in this directory.

  6. Edit the index.css file.

  7. Go to company_logo and replace the existing URL reference with a reference to the new logo image file.

  8. Save the changes in the file..

  9. In SmartConsole, install policy.

Note - No spaces are allowed in the <skin_name>.

Configuring the Languages Option

To configure the Languages Option:

The languages directory is located inside the $FWDIR/conf/extender directory on the Security Gateways.

There may be two subdirectories:

  • chkp - Contains languages that Check Point provides by default. During upgrade, this subdirectory may be overwritten.

  • custom - Contains languages defined by the customer. If custom does not exist yet, create it. During upgrade, this subdirectory is not overwritten. New languages are added in this subdirectory.

Disabling a Language

  1. Enter the specific language subdirectory, in the custom directory that is to be disabled (if it exists) and create a file named disable. This file may be empty.

  2. If the specific language does not exist in the custom directory, create it and then create a file within it named disable.

  3. In SmartConsole, install policy.

    The next time that the user connects to the SSL Network Extender portal, this language is not be available.

Adding a Language

  1. Enter the custom subdirectory.

  2. Create a folder with the applicable language name.

    Note - Make sure this name is not already used in chkp. If it is, the new language definition overrides the existing language definition (as long as the new language definition exists). Once you have deleted the new language definition, the chkp language definition is used again.

  3. Copy the messages.js file of an existing chkp language to this directory.

  4. Edit the messages.js file and translate the text bracketed by quotation marks.

  5. Save the changes in the file.

  6. In SmartConsole, install policy.

Example

  1. cd $FWDIR/conf/extender/language

  2. mkdir custom

  3. cd custom

  4. mkdir <language_name>

  5. cd <language_name>

  6. cp -v ../../chkp/english/messages.js .

  7. Edit the messages.js file and translate the text bracketed by quotation marks.

  8. Save the changes in the file.

  9. In the custom/english/messages.js file, add a line as follows:

    <language_name>="translation of language_name";

    Note - No spaces are allowed in the <language_name>.

  10. Install the Access Control policy.

Modifying a Language

  1. Enter the custom subdirectory.

  2. Create a folder with a language name that matches the chkp language folder to be modified.

  3. Create an empty messages.js file, and insert only those messages that you want to modify, in this format:

    <variable_name>="<applicable_text>";

    Note - For reference, refer to the messages.js file, located in chkp/<language>.