HomeHome ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles Request New ArticleRequest New Article
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon Knowledge Base Information
DrillDown Icon Cyberoam Security Appliances (UTM and NGFW)
DrillDown Icon FAQs on Cyberoam and Sophos Firewall
DrillDown Icon Vulnerability Security Advisories
DrillDown Icon Best Practices & Policies
DrillDown Icon Protect Your Cyberoam Appliances from Power Fluctuations
DrillDown Icon Technical Library
DrillDown Icon Deployment
DrillDown Icon Registration & Licensing
DrillDown Icon System
DrillDown Icon Objects
DrillDown Icon Network
DrillDown Icon Identity
DrillDown Icon Firewall
DrillDown Icon VPN
DrillDown Icon IPS
DrillDown Icon Web Filter
DrillDown Icon Application Filter
DrillDown Icon Web Application Firewall (WAF)
DrillDown Icon IM
DrillDown Icon Quality of Service (QoS)
DrillDown Icon Anti Virus
DrillDown Icon Anti Spam
DrillDown Icon Logs & Reports
DrillDown Icon Clients
DrillDown Icon Cyberoam Transparent Authentication Suite (CTAS)
DrillDown Icon Install and Configure Cyberoam iAccess for iOS
DrillDown Icon Install and Configure Cyberoam General Authentication Client for Mac OS
DrillDown Icon Install and Configure Cyberoam iAccess authentication client for Android OS
DrillDown Icon Install and Configure Cyberoam General Authentication Client for Windows OS
DrillDown Icon Install and Configure Cyberoam General Authentication Client for Linux OS
DrillDown Icon Can we bind MAC Addresses to users using Captive Portal Authentication?
DrillDown Icon Whom should I contact to get the Subscription Key for IPSec VPN client?
DrillDown Icon Errors
DrillDown Icon Cyberoam Maintenance
DrillDown Icon Compatibility
DrillDown Icon Archives
DrillDown Icon Visio Stencils for Cyberoam security appliances
DrillDown Icon Product Technical Support
DrillDown Icon Cyberoam Virtual Security
DrillDown Icon Cyberoam iView
DrillDown Icon Cyberoam Central Console
DrillDown Icon Cyberoam's On-Cloud Management Service
  Subscribe Print PreviewPrint Current Article and All Sub-Articles
Rate Icon Rate Icon Rate Icon Rate Icon Rate Icon
 
Install and Configure Cyberoam General Authentication Client for Linux OS

Applicable Cyberoam Version: 10.00 onwards

Applicable Linux Version(s): Redhat 6 (Santiago), Cent OS 6, Ubuntu 12.04 LTS, Debian 3.7.2.i686, Debian 3.7.4.1 i686, Linux Fedora 15 OS, Ubuntu 10.04 OS, Ubuntu 13.10 OS

Cyberoam General Authentication Client for Linux OS enables users using Linux Operating System to logon to Cyberoam.

 

To install the GAC on your Linux system, follow the steps given below

 

Step 1: Download Corporate Client for Linux OS from www.cyberoam.com/cyberoamclients.html. 

 
 
 
This will save the setup program in the compressed format.
 
Administrative right is required to install Cyberoam Corporate Client for Linux.
 
 
 
Copy the downloaded file on the user machine and perform steps 2 to 5.

Step 2
: Extract saved file with the following command:


tar xvfz CyberoamLinuxClient.tar.gz
 
This will create a directory named "crclient" with two files - “crclient” and “README” file in the “crclient” directory.


Step 3:
To logon to Cyberoam, execute following command:

./crclient -u <username> -i <interface> 

Example: ./crclient -u johnsmith -i eth0

It will prompt for Cyberoam server IP address and password of the username specified as configuration file is not created.

Above process will create following files:

  • .Conf file:<user'sHomeDirectory>/crclient.conf
  • Log file: /var/log/crclient.log
  • Pid file: /tmp/crclient.pid

Step 4:
Logout using following command:
 

./crclient -l <username>

 

Example: ./crclient -l johnsmith

 

This completes the installation.



Step 5: Configuration
 
Installation automatically creates the config file with the default parameters with the name crclient.config under the user’s home directory. You can edit default configuration file, by opening crclient.config file using any of the Editors. Configuration file includes the below shown parameters.
 

Example of Configuration File


AskonExit                        0

AutoLogin                         0

FirstTime                          1

Password

Port                                  6060

SavePassword                   0

Server 192.168.1.1

User tmpuser

ShowNotification                1

LiveRequestTime                180

AlreadyLoggedIn                 0

VersionId                           1

Versioncrclient1.1

 
When User logs on, Configuration file is first searched in /etc directory, if not found, searches in the user's home directory. If the configuration file is not found at both the places, a file is created in the user's home directory by accepting the essential parameters from the User. Following options are provided in the Cyberoam client:
 
Parameter
Description
-u
Responsible for sending a login request to the server and requires username as a parameter
-s
Use to set preferences for the client. Preferences such as AskonExit, AutoLogin, ShowNotification and Server Address can be set using this option
-I
Use to send a logout request to the server.Multiple Login mode requires
“username” as an argument
-h
Provides help for the client
-d
Use to specify the location for log file
-v
Use to set the verbose mode on. This option is for debugging
-V
Provides Current Version information
-f
Use to specify the locationfor the configuration file
  -i   Use to specify interface to which user is to log on


Note

Check for the file “crclient.pid”, if system crashes or user is not able to login. If this file is present then Cyberoam Client will not come up. Remove the file for successful logon.

This completes the installation and configuration.

After configuration, when user tries to logon to Cyberoam using following command: ./crclient -u <username> -i <interface>, user will not be prompted to enter Cyberoam server IP address as configuration file already exits.

                                                                                                                                            


                                                                                                                                               Document version: 1.3 - 5 August, 2014
 
Attachments
Article ID: 1870