User/Device Authorization

Tell us in greater detail how the authorization?
As client and server communicate with one another using the authorization?

#2

IN our organization we have next scheme: 1 server terminal with 5 users which have 5 token. How using the authorization that user random stranger token is not connected

#4

how vhuix64 defines authentication method?

you need to register separately each vhuiserver key? if there are 5 users and 1 terminal server, as there is authorization?

#5

You cannot setup authorization from the client you need to set it up from the server by using bash on the command line and vi to create the script as shown in the example at that link.

If you have a NAS there is no way currently to setup authentication via a GUI, you need ssh access to your NAS and then just follow the normal linux commands to create the script. And dont forget to make the script executable or it wont run.

#7

You need to setup the authentication on the linux server...i dont even have a windows server?

My suggestion is just just set it up on the linux server and then see what it does, then you can ask questions

#8

I understand that the authorization script is configured on the linux server.
I don't understand how it look for user of terminal server .
How user by the name of Vasily get access only to its own USB token.
And at the same time User by name Peter use own usb token, but can't use a USB token of Vasily.
Can you give an example of such a code in the authorization script?

#9

Its already there in the example, the virtualhere client automatically passes in the username of the user who is running the client. The username is the username that the person uses to login to windows or osx or linux. So you just parse that name like i did with "michael" in the example script, it is passed in as CLIENT_ID argument $3 in that script

e.g in the documentation at that link, there is the text

. The CLIENT_ID is passed in by the VirtualHere client to the server. It is automatically set to the same username used to login to the current operating system session under Windows / OSX / Linux.

#10

do I understand correctly, each user must run the client for authorization?
Now on the terminal server we can run only one copy of the client on behalf of one user, if we run the client in the session of another user on the same terminal server, the client does not start.

#11

Your terminal sounds like it is "Session based", rather than Virtual Machine based, therefore you can only run one virtualhere client on the server. I havent yet implemented RDP passthrough to support session based terminals.

Some customers have done it via freerdp and virtualhere via the urbdrc channel that you can add to the freerdp server