# Linux Vision Clients Auto login and security

**URL:** <https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [July 28, 2022, 6:42pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425 "2022-07-28T18:42:20Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jason\_kensett](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jason\_kensett](https://forum.inductiveautomation.com/u/jason_kensett)\
**Post date:** [July 28, 2022, 6:42pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/1 "2022-07-28T18:42:20Z")

</div>

Vision w/Ignition8.1.17  
I am using cheap x64 pc’s with Linux mint mate and I am having issues figuring out the auto login. If I set the auto login to enable in the project the client will launch fine and I can get it to load the proper window with a client script using host or IP.  
I can’t figure out how to make the non “guest” clients have to login without an error. Do I have to set this up on a welcome page? I would think that I could do this without letting them “in the door” before they have to authenticate.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 28, 2022, 6:51pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/2 "2022-07-28T18:51:00Z")

</div>

OS login and Vision client login are two totally independent operations. It sounds like you are mixed up about which is which. Your Vision client can use [system.security.switchUser](https://docs.inductiveautomation.com/display/DOC81/system.security.switchUser) to change the logged-user for Vision (starting from your own custom login window), but you won’t be changing the OS user. This isn’t any different from Windows.

For kiosk duty, you should create a custom Xsession and login `.desktop` file for SDDM to use, configured to auto-login and re-login an unprivileged OS user upon system startup. That custom Xsession would invoke the Vision Client Launcher with a full-screen project instead of starting the usual desktop.

---

<div class="post-metadata">

**Author:** ![jason\_kensett](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jason\_kensett](https://forum.inductiveautomation.com/u/jason_kensett)\
**Post date:** [July 28, 2022, 7:05pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/3 "2022-07-28T19:05:55Z")

</div>

I might not have tried the switch user. I was trying not to use a custom login window because I thought I read that it wasn’t preferred/supported?  
So I would auto login to an unrestricted window, use a client start up script to send my clients to their displays and then switchUser everyone else for verification?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 28, 2022, 7:13pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/4 "2022-07-28T19:13:53Z")

</div>

Yes. Note that all of the Vision operations are the same whether Windows or Linux.

---

<div class="post-metadata">

**Author:** ![jason\_kensett](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jason\_kensett](https://forum.inductiveautomation.com/u/jason_kensett)\
**Post date:** [July 28, 2022, 7:25pm UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/5 "2022-07-28T19:25:23Z")

</div>

Thanks, I will give this a try. oh, and I tried the custom Xsession and failed. I did learn a ton about Linux over the last few days though. I will give it another try later, but for now I have something that will work without me baby sitting them all day. I want close to unbreakable though because they will get messed with.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 29, 2022, 12:24am UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/6 "2022-07-29T00:24:31Z")

</div>

If you get the custom Xsession working, and it launches the full-screen vision client directly, if the user does manage to exit entirely, it will simply take them back to the OS login screen. Which can then auto-login again. As close to unbreakable as can be.

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [July 29, 2022, 4:01am UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/7 "2022-07-29T04:01:30Z")

</div>

@pturmel what is your preferred Linux OS for this sort of stuff?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 29, 2022, 11:43am UTC](https://forum.inductiveautomation.com/t/linux-vision-clients-auto-login-and-security/62425/8 "2022-07-29T11:43:52Z")

</div>

Xubuntu for kiosks. Kubuntu for proper workstations. Raspian for RPis.
