Cryptzone Support

 
If you wish to submit a support ticket please sign in to your customer portal or use the “submit a ticket” button at the top menu.
If you need to find documentation about our Sheriff Suite please login to the Hive- Click Here

 

Article

Handling_more_than_one_type_of_user_agclientproperties

« Go Back

Information

 
Article Number000001064
Article

In some situations it may be useful to have the client behave differently depending upon what type of user connecting to the system. One might have a very minimalistic client for most users and a client with all settings available for power users or technical staff.

It may also be useful to have one single server display different corporate logotypes depending upon the situation.

Both these behaviors can be implemented.

Overview

The AppGate server's deployment web can be configured to optionally hand out special versions of files. This is controlled by looking at the IP address which was used to access the AppGate server. By setting the server up to listen to more that one IP address and then directing different user categories to the appropriate IP address each category gets their adapted versions where needed.

The default pages of the deployment web are located in /var/opt/appgate/webroot.local. When a client connects to the AppGate deployment web the server looks in this directory for sub-directories named as the IP number to which the connection was made. If such a sub-directory exists, any content found there will be used instead of the corresponding content in the default directory.

How to do it

  1. First you need to assign a new IP number to the AppGate server on the external network. So if the current IP is 10.0.0.1 let's say we assign 10.0.0.2 to the AppGate as well. Then you need to make sure the AppGate is listening to that IP.
    1. In the AppGate console, go to System Settings->Network/Cluster Management->System:... 
    2. Right click on the external device (ex called Net 0, Gb 1 or e1000g0 depending upon what your machine is) you can create a Virtual Interface. 
    3. Activate the new interface and setup the hostname and IP address and select the external network as network. 
    4. Commit.
  2. You can now try to reach the AppGate on 10.0.0.2, you should see a normal AppGate page.
  3. Start a terminal from the console
    1. Become root (su)
    2. Go to /var/opt/appgate/webroot.local (cd /var/opt/appgate/webroot.local).
    3. Create a directory 10.0.0.2 (mkdir 10.0.0.2).
    4. Go into that directory (cd 10.0.0.2) and create another directory called webstart (mkdir webstart).
    5. Go into that directory (cd webstart) and create a file called agclient.properties (touch agclient.properties).
  4. In the AppGate console, go to Clients->Client Configuration Files. Select the new file from the drop-down menu. Here you can setup the configuration you want. For you power users. Remember to save once you're done.

The result you now have two addresses for the AppGate server each handing out a different agclient.properties. This file is the one controlling the behavior of the client. So normal users go to the old address 10.0.0.1, power users go to 10.0.0.2.

If you instead of creating and adding content to webstart you add a new logotype in 10.0.0.2 this will be used instead of the default one which can be used to achieve customized branding.

Related File 
Additional Files 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255