eG Self-Service Portal

On Unix, all ports below 1024 are privileged ports. Only super users or users authorized to access this port will be able to bind to these ports. If you wish to have the eG manager listening on a privileged port, you will need to follow the procedure listed below.

When the eG manager is installed on Solaris 10 or higher, you can install the eG manager and have it configured to listen to a privileged port (e.g., 80 or 443). Before starting the manager, login to the Solaris server as a super-user and run the following command to instruct the operating system to allow the eG user to open a privileged port:

usermod -K defaultpriv=basic,net_privadd <EG_USER>

Log out and log back in as the eG user, and then, start the eG manager.

On Linux systems, follow the steps below:

• Install the eG manager on a port higher than 1024 – e.g., 7077. 
• Use the iptables command to set up redirection from a privileged port to the port that the eG manager is using. For example, suppose you have installed the eG manager on port 7077 with SSL support and you would like the manager to listen on port 443; then, do the following.

                     - Execute the iptables command as below on the Linux system hosting the eG manager. 

                       These commands should be executed from a super-user account.

iptables -t nat -A OUTPUT –d <IP/HOSTNAME OF THE EG MANAGER> -p tcp --dport 443 -j REDIRECT --to-ports 7077

iptables -t nat -A PREROUTING -d <IP/HOSTNAME OF THE EG MANAGER> -p tcp --dport 443 -j REDIRECT --to-ports 7077

                     - Once these commands are executed, the eG manager will be accessible on port 443 as well.

• Entries configured using iptables are lost when the manager reboots. To save the iptables configuration, do the following:
  

                                        /sbin/iptables-save > /opt/egurkha/iptables.fw

                     - Edit the file /etc/rc.local and append the following line to this file  

                                       /sbin/iptables-restore < /opt/egurkha/iptables.fw

Now, even if the eG manager system is rebooted, the iptables configuration is restored.