limiting login names on certain workstations

Find and share HowTos to various installations / configurations!
5 posts • Page 1 of 1
tmalone
Posts:192
Joined: Mon Nov 22, 2010 11:21 pm

limiting login names on certain workstations

Post by tmalone »

I am using clients with -ssa (server side authentication) in 3.18

We have requirements that some workstations cannot have a login with control (view only).

Is there a way to limit the logins on a workstation? or create a view only client?

FYI, I have looked at the LoginFramework and I do NOT want to invent my own security. Can I leverage this to check the login and stop anything but "guest"?

tmalone
Posts:192
Joined: Mon Nov 22, 2010 11:21 pm

Re: limiting login names on certain workstations

Post by tmalone »

I found this wonderful concept, "To open a desired panel after login" from the help. It is a parameter in the UI shortcut.

This works fine and I get my panel.

Once I have my panel, I then want to continue to the topology that I have setup. The help hints that you would use afterLogin("operator", "", "en_US.utf8") but that call just errors out with all sorts of "variable not defined". I guess this is not a function call for users?

How can I continue to open my topology after my special panel?

tmalone
Posts:192
Joined: Mon Nov 22, 2010 11:21 pm

Re: limiting login names on certain workstations

Post by tmalone »

I tried to just used the function: setUserId(4096, "") on the init of the topology info panel, but it fails, probably because of -SSA

tmalone
Posts:192
Joined: Mon Nov 22, 2010 11:21 pm

Re: limiting login names on certain workstations

Post by tmalone »

also tried using the auto-login features "-p vision/login.pnl,auto,$user:guest,$pwd: " and that fails with -ssa.

Is there a way to auto-login in SSA?

tmalone
Posts:192
Joined: Mon Nov 22, 2010 11:21 pm

Re: limiting login names on certain workstations

Post by tmalone »

I have settled on a solution that seems to work. If the workstation is one of our read-only stations, we can check for the hostName on topology startup. If it is one of those stations, we run STD_LogoutCurrentUser() and disable the ability to click login buttons. NOTE: if you have to do this, you must put a delay(2,0) before the logout function to let the client finish initializing to avoid errors.

5 posts • Page 1 of 1