HP ProLiant xw2x220c Remote Graphics Software 5.3.0 User Guide - Page 46

RGS security features, authentication uses the Pluggable Authentication Module PAM.

Page 46 highlights

2-23 RGS security features Because of the distributed nature of an RGS connection, providing connection security is critically important. RGS implements many features to provide connection security, including: • Authentication: When a local user attempts to connect to a Remote Computer, the user credentials are validated using the native authentication method on the Remote Computer. If the credentials are not authenticated, the connection is closed. On Windows, authentication uses NTLM or Kerberos. On Linux, authentication uses the Pluggable Authentication Module (PAM). • Authorization: Multiple connections to the same Remote Computer are only allowed if the user logged into the desktop of the Remote Computer (primary user) allows the connection. When another user attempts to connect to the Remote Computer, an authorization dialog is displayed on the desktop of the Remote Computer that asks whether the new user should be allowed to connect. • Automatic desktop locking: The desktop of the Sender system locks when the primary user disconnects. This prevents non-primary users from being able to interact with a remote session after the primary user has disconnected. This feature is supported on Windows. On Linux, this feature is supported on the Gnome, KDE, and CDE desktop environments. • Automatic disconnect: On Linux, all Receivers will disconnect when the primary user disconnects. This prevents non-primary users from interaction with a remote session after the primary user disconnects. • Automatic disconnect of non-primary users on Login: All non-primary users are disconnected when a login event occurs. Only the primary user remains connected when the desktop of the remote computer is logged in. • Automatic disconnect on log off: All Receivers are disconnected when the primary user logs off of the remote desktop. This can be disabled by setting the Rgsender.IsDisconnectOnLogoutEnabled Sender property to "0". See the Sender properties for more information. • Connection status: On Windows, a desktop icon in the application tray animates when other users are connected. Likewise, on Linux, the Sender GUI animates. • Collaboration notification: See Section 5-5-2, "Collaboration notification." • Connections are not allowed when an iLO remote console is enabled: If the iLO remote console is enabled on a HP Blade Workstation, connections to the blade using RGS are denied. • Disconnect all: All Receivers can be easily disconnected using the Sender GUI. This is useful when hosting a collaboration session, such as in a classroom environment, and the session ends. On Windows, the Sender GUI is an icon in the system tray. On Linux systems, the GUI is an application on the desktop. Simply rightclick on the GUI and select "Disconnect All Receivers". • Remote Keyboard/Mouse: The Sender GUI can enable or disable mouse and keyboard input for all nonprimary users. • Single user connection: A user, identified by a username, is only allowed one connection to a RGS Sender. If the same username connects more than once to a Sender, the previous connection drops and the new connection continues on. If several users attempt to share a username, only one connection is active at a time. • SSL encryption: SSL securely encrypts all data transmitted between a Receiver and Sender pair. RGS overview 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

RGS overview 46
2-23 RGS security features
Because of the distributed nature of an RGS connection, providing connection security is critically important. RGS
implements many features to provide connection security, including:
Authentication:
When a local user attempts to connect to a Remote Computer, the user credentials are
validated using the native authentication method on the Remote Computer. If the credentials are not
authenticated, the connection is closed. On Windows, authentication uses NTLM or Kerberos. On Linux,
authentication uses the Pluggable Authentication Module (PAM).
Authorization:
Multiple connections to the same Remote Computer are only allowed if the user logged into
the desktop of the Remote Computer (primary user) allows the connection. When another user attempts to
connect to the Remote Computer, an authorization dialog is displayed on the desktop of the Remote
Computer that asks whether the new user should be allowed to connect.
Automatic desktop locking:
The desktop of the Sender system locks when the primary user disconnects. This
prevents non-primary users from being able to interact with a remote session after the primary user has
disconnected. This feature is supported on Windows. On Linux, this feature is supported on the Gnome,
KDE, and CDE desktop environments.
Automatic disconnect:
On Linux, all Receivers will disconnect when the primary user disconnects. This
prevents non-primary users from interaction with a remote session after the primary user disconnects.
Automatic disconnect of non-primary users on Login:
All non-primary users are disconnected when a login
event occurs. Only the primary user remains connected when the desktop of the remote computer is logged
in.
Automatic disconnect on log off:
All Receivers are disconnected when the primary user logs off of the remote
desktop. This can be disabled by setting the
Rgsender.IsDisconnectOnLogoutEnabled
Sender
property to "0". See the Sender properties for more information.
Connection status:
On Windows, a desktop icon in the application tray animates when other users are
connected. Likewise, on Linux, the Sender GUI animates.
Collaboration notification:
See Section 5-5-2, “
Collaboration notification
.”
Connections are not allowed when an iLO remote console is enabled:
If the iLO remote console is enabled on
a HP Blade Workstation, connections to the blade using RGS are denied.
Disconnect all:
All Receivers can be easily disconnected using the Sender GUI. This is useful when hosting a
collaboration session, such as in a classroom environment, and the session ends. On Windows, the Sender
GUI is an icon in the system tray. On Linux systems, the GUI is an application on the desktop. Simply right-
click on the GUI and select "Disconnect All Receivers".
Remote Keyboard/Mouse:
The Sender GUI can enable or disable mouse and keyboard input for all non-
primary users.
Single user connection:
A user, identified by a username, is only allowed one connection to a RGS Sender. If
the same username connects more than once to a Sender, the previous connection drops and the new
connection continues on. If several users attempt to share a username, only one connection is active at a
time.
SSL encryption:
SSL securely encrypts all data transmitted between a Receiver and Sender pair.