I would like to be able to connect to Royal Server without storing my AD password in the local document. It should simply use my login session on the local computer to authenticate.
I know I can create a credential object and encrypt the local document, but that creates an extra step, and forces me to create a duplicate credential object.
The document that we open on the Royal Server is integrated with our password manager, which also has a credential for our Windows user account. Being forced to also store it locally, means there is another place it needs to be updated when we change passwords. And if we have Royal TS installed on multiple machines, that further compounds the duplicate entries.
We have this request as well, especially coming from RemoteDesktopManager where we used integrated autentication against a SQL datasource makes this a bit more cumbersome for our staff to update passwords regularly in documents.
Hi,
I think we discussed this on a different thread already. Royal Server does not use MS SQL in the backend, so built-in authentication is not an option. Also, for some Royal Server operations - especially related to management tasks - we actually need to impersonate the user on the server. This and also many other factors (like making Royal Server cross platform) prevents us from using built-in authentication. AFAIK, there’s no public API to pass on a token to a server and impersonate that user based on that token.
Regards,
Stefan