Appendix C – Integration with plugin use case

Actors:

User, User Portal, Spark Gateway

Preconditions:

User Portal:

SparkView:

Basic flow:

  1. User login to User Portal.
  2. User Portal encrypt the user credential and other information like User Portal session id as a token string, for example:
    'user=domainUser&pwd=domainPassword&domain=domain&session=id’.
  3. User Portal construct a connection link and display it to user:
    http://gateway/rdpdirect.html?token=myEcryptedToken&displayName=nameOnBrowserTitle&otherParameters; or use the Spark View JS library directly to create a connection:
    var rdp = new svGlobal.Rdp(‘wss://gateway/RDP?token=myEycryptedToken&..’, width, height, color);
  4. User click the link and connect.
  5. SparkView plugin decrypt the token, verify the user session (optional) and put the decrypted RDP parameters back (Please check the plugin example for details: http://www.remotespark.com/Plugin.zip)

Pros:

Cons:

Both use cases are recommended. You can also consider to use them together (symlink with plugin), so user credentials can be encrypted and don’t need to be sent to the client side.

If User Portal cannot have the user credentials in plain text, you can consider to create a temporary windows user account for every user and remove this account later.


Revision #2
Created 8 April 2022 11:50:26 by Guest
Updated 8 April 2022 11:52:29 by Guest