# Is there a way to pass in the username and password into the client laucher

**URL:** <https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212>\
**Category:** Ignition\
**Created:** [March 4, 2018, 8:21pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212 "2018-03-04T20:21:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![codersmurf](https://avatars.discourse-cdn.com/v4/letter/c/df788c/32.png) [@codersmurf](https://forum.inductiveautomation.com/u/codersmurf)\
**Post date:** [March 4, 2018, 8:21pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212/1 "2018-03-04T20:21:36Z")

</div>

Wanted to automate this for some of the less computer literate users. We have a bunch of logins that will change the interface from that login and it would kickass if I could have the login be passed into the client launcher and I’ll have the vnc start the scada right to where they are ready to go. Thanks

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 4, 2018, 9:15pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212/2 "2018-03-04T21:15:28Z")

</div>

There is not a recommended way to do this.

The way people accomplish this anyway is auto-login a guest and build their own login screen.

---

<div class="post-metadata">

**Author:** ![codersmurf](https://avatars.discourse-cdn.com/v4/letter/c/df788c/32.png) [@codersmurf](https://forum.inductiveautomation.com/u/codersmurf)\
**Post date:** [March 5, 2018, 5:07pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212/3 "2018-03-05T17:07:54Z")

</div>

I saw an article for this but it was from like 2 years ago, it didn’t even cross my mind such a simple feature wouldn’t be implemented yet. I didn’t analyse it too much but it seemed like security was out the window with the way they did it, so I would just maintain the login info in tags instead of the gateway?

---

<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:** [March 5, 2018, 5:33pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212/4 "2018-03-05T17:33:19Z")

</div>

> [@codersmurf](#):
>
> such a simple feature wouldn't be implemented yet

Huh?  
It's really hard to do this securely. Anything that involves placing a password into a command line makes that password visible to other processes on the machine.  
Kevin is referring to setting your project to auto-login with an unprivileged Ignition user, who is shown only the read-only information available to everyone. With some user interface that allows the user to log in with more privileges, and/or check client machine characteristics in scripting to offer additional functionality. No exposed passwords -- certainly not storing in tags.

---

<div class="post-metadata">

**Author:** ![codersmurf](https://avatars.discourse-cdn.com/v4/letter/c/df788c/32.png) [@codersmurf](https://forum.inductiveautomation.com/u/codersmurf)\
**Post date:** [March 5, 2018, 5:36pm UTC](https://forum.inductiveautomation.com/t/is-there-a-way-to-pass-in-the-username-and-password-into-the-client-laucher/17212/5 "2018-03-05T17:36:23Z")

</div>

So the security is at a higher level, it’s more for security between users that I need. I don’t want one user able to login as another user. Like I said, with automation most users are barely able to use computers and computer like devices, so user names and passwords are constantly lost written down in plain view, etc.
