A virtual channel is a session-oriented and bidirectional error-free transmission connection that application layer code can use to exchange custom data packets between a terminal server and a terminal client.
SecureLogin employs this technology to allow users to single sign-on to various Published Application or Remote Desktop logins.
SecureLogin Terminal Server single sign-on has three major components:
SecureLogin uses the following process:
If the platform doesn't exist, the VCD reverts to the generic platform name.
If the generic platform name doesn't match the requested platform (tree or domain), the VCD displays a dialog box to prompt the user to enter NDS, eDirectory, or NT credentials. The credentials that are expected depend on whether the request is coming from a server with a Novell Client or from an NT/2000 server. The collected credentials are then sent to the server for verification.
When the user enters and accepts the credential dialog box, a hidden application is created for the next authentication request.
If the user chooses to abort entering credentials, the server login box appears as usual.
NOTE: SecureLogin doesn't currently handle the actual password change process. Therefore, SecureLogin does not send back the new password when it is changed on the Citrix server. However, when the password stored in slbroker.exe is invalid because of a recent password change done on the Citrix Server, the user is prompted to enter login credentials again. After the new password is verified, it is then sent back to the VCD to update slbroker.exe.
The server detects whether the ICA protocol is present or not. If the ICA protocol is present, the server loads it. If the client is trying to establish a session by using the RDP protocol, the server loads the RDP protocol and the session begins. After the server is installed, it automatically responds to the RDP or ICA protocol.
By default, the Auto Detection feature is on.
Windows NT* 4.0 Terminal Server Edition (RDP 4.0) does not support the virtual channel operation. If the client tries to establish a session by using the RDP protocol, Windows NT 4.0 Terminal Server Edition won't respond to the client.