ThinRDP Server incorporates a mechanism to validate users in a corporate environment so that the user will not need to authenticate every time they access ThinRDP.
How to authenticate against ThinRDP from external applications:
The authentication against ThinRDP Server can be done using:
| • | username and password or |
| • | username and an ApiKey. |
Every time you call ThinRDP Server, you can send within its URL the authentication information. The URL format to authenticate this way is presented below:
http[s]://[username]:[password or apikey]@127.0.0.1:8443
|
The External Authentication requires the option "Use Standard browser authentication dialog" to be set as true. |
Encryption:
Whether the authentication is done using password or apikey, the secrecy of this data is indispensable. That is why ThinRDP enables external applications to dynamically negotiate a key to use the Diffie Hellman Key Exchange method for posterior encryption.
Demo:
The IIS asp.net demo application is an example on how to authenticate and encrypt the exchanged data.
Read the next topics to find out how to configure and use these ThinRDP mechanisms:
Learn also about these single-sign-on methods ThinRDP is compatible with: