Article ID: 3390, created on Nov 30, 2007, last review on May 11, 2014

  • Applies to:
  • H-Sphere

Resolution

Sometimes you may need to allow selected customers SSH access to your server. Such authorized users can run shell scripts, and have other extensive privileges. To allow your customers request shell access and, if granted, operate their accounts through shell, make sure to include it in plan wizard.

Please be careful with choosing who can be given SSH access permission to reduce the risk of system functionality and security problems.

Important: Resellers also can offer Shell access which can be included in plan wizard. But they can't grant/deny user requests from the reseller admin area. Instead, end-user requests are sent to the main admin. Once the request is granted or denied, the reseller and its users receive the corresponding email notification.

To view shell access requests from your customers:

  1. Select Shell Request Manager in the INFO menu:

  2. On the Shell request manager page you will see:

    - Shell Access Notifications: turn it ON and your end-users will get notifications stating that shell access was granted or denied
    - Accounts with Shell Access Requested: it shows how many user requests you have recieved. You can allow or prohibit the access.
    - Accounts with Shell Access Enabled: it shows the accounts that have been granted shell access

To allow shell access:

  1. Go to Shell Requests Manager in the INFO menu.
  2. Click Allow in the Action area. The account will appear in the Accounts with Shell Access Enabled section and user will get the notification.

To prohibit shell access:

  1. Click Prohibit in the Action area.
  2. Enter the prohibit reason in the form that appears:
  3. Click Submit. The account will disappear from Shell Request Manager and user will get the corresponding notification.

You can also disable shell access for the accounts with previously granted access. To do it, click Disable Access and account will disappear from Shell request manager.

f213b9fa8759d57bee5d547445806fe7 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF