HP Xw460c Remote Graphics Software 4.2.0 User Guide - Page 93

Using Single Sign-on

Page 93 highlights

Using Remote Graphics Software Using Single Sign-on When RGS Single Sign-on is not installed, users are normally required to authenticate twice when connecting - once to connect from the RGS Receiver to the RGS Sender (RGS connection) and another to log into or unlock the remote desktop (Desktop session). When Single Sign-on is installed, users will normally need to enter their credentials only once. The user will be prompted on the RGS Receiver to enter their credentials. These credentials will be used to authenticate the connection to the RGS Sender. If the user is authenticated on the sender, the same credentials will be used to silently log into or unlock the user onto the users desktop. Single Sign-on will only occur when the Sender is in one of two states - the logged off state or the locked desktop state. These two states are WinLogon states, and are controlled by the WinLogon.exe process running on the Sender system. WinLogon.exe is the Window's logon manager and is the process responsible for managing user logon and logoff. The WinLogon.exe process controls these states, more formally known as WlxDisplaySASNotice and WlxDisplayLockedNotice states. When the remote desktop is in the logged off state (WlxDisplaySASNotice), the following dialog is present on the remote desktop: When the remote desktop is in the locked desktop state (WlxDisplayLockedNotice), the following dialog is present on the remote desktop: 85

  • 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

Using Remote Graphics Software
85
Using Single Sign-on
When RGS Single Sign-on is not installed, users are normally required to
authenticate twice when connecting -
once to connect from the RGS Receiver to the
RGS Sender (RGS connection) and another to log into or unlock the remote desktop
(Desktop session).
When Single Sign-on is installed, users will normally need to enter their credentials
only once. The user will be prompted on the RGS Receiver to enter their credentials.
These credentials will be used to authenticate the connection to the RGS Sender. If
the user is authenticated on the sender, the same credentials will be used to silently
log into or unlock the user onto the users desktop.
Single Sign-on will only occur when the Sender is in one of two states - the logged
off state or the locked desktop state. These two states are
WinLogon
states, and are
controlled by the
WinLogon.exe
process running on the Sender
system.
WinLogon.exe
is the Window's logon manager and is the process
responsible for managing user logon and logoff
.
The
WinLogon.exe
process controls
these states, more formally known as
WlxDisplaySASNotice
and
WlxDisplayLockedNotice
states.
When the remote desktop is in the logged off state (
WlxDisplaySASNotice
), the
following dialog is present on the remote desktop:
When the remote desktop is in the locked desktop state (
WlxDisplayLockedNotice
),
the following dialog is present on the remote desktop: