Configuring Built-In Secure Access

Built-in secure access methods are managed by User Role and are globally scoped within an Application Profile.

To create a built-in secure access policy, navigate to Access Policy Management > Access Policies and click "Add Access Policy".  This brings up a page for you to configure the new policy settings:

• Select "Remote Desktop Access" as the Access Policy Type

• Enter a descriptive Access Policy Name

• Select the User Role that this policy applies to

• In "Default Server Function", select "Access Desktop"

• Configure the Access Control List to allow access for the desired servers

Click "Next" to advance to the next configuration page, which allows you to configure access options for each individual server.

Here you may assign different access methods for different targets.  The supported access methods include:

• Connect View - VNC/RDP, which enables VNC or RDP as appropriate for the target server OS

• Connect View - NoMachine, which  enables NX access (you must install the NX client/server before using this function)

• Secure Shell, which enables ssh access (supports password- or key-based authentication)

• VNC Active Join, which enables a user to connect to a VNC session started by another user

• RDP Console, which enables the RDP Console

• VNC Invite, which enables users to invite other users to a  share a collaborative VNC session

• Remote GDB, which enables a user to begin a remote debugging session over CoIP using GDB

The Server Function selector chooses which license type should be checked out; the Access Desktop license type supports single user use (e.g. multiple VNC sessions, but for one CoIP user), while the Access Server license type supports multiple users (e.g. multiple VNC sessions for multiple CoIP users).

Click "Save" to save the policy.  The policy is immediately activated and becomes visible for users with the specified User Role.