# Login Disable for launching Application

**URL:** <https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658>\
**Category:** Ignition\
**Created:** [July 7, 2022, 9:13pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658 "2022-07-07T21:13:42Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirill\_ivachkine](https://avatars.discourse-cdn.com/v4/letter/k/5f9b8f/32.png) [@kirill\_ivachkine](https://forum.inductiveautomation.com/u/kirill_ivachkine)\
**Post date:** [July 7, 2022, 9:13pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/1 "2022-07-07T21:13:42Z")

</div>

I am very new to this platform. I’ve Used windows to create a simple Ignition Edge Panel application that is able to read and write to/from an AB PLC and I need to be able to launch it automatically without any login function. Is there a way to do this? Any help is greatly appreciated

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [July 7, 2022, 9:43pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/2 "2022-07-07T21:43:25Z")

</div>

Set permissions to Public in Project Properties under Project menu in Designer:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/1/31d5e64ce998af6f58d27aab25c4e395454c9399.png)  
As noted by @paul-griffith, this answer applies to Perspective. See @r.castro’s answer below for Vision.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 7, 2022, 9:44pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/3 "2022-07-07T21:44:55Z")

</div>

If you’re using Perspective.

If you’re using Vision, you can enable auto-login in the project properties.

---

<div class="post-metadata">

**Author:** ![kirill\_ivachkine](https://avatars.discourse-cdn.com/v4/letter/k/5f9b8f/32.png) [@kirill\_ivachkine](https://forum.inductiveautomation.com/u/kirill_ivachkine)\
**Post date:** [July 7, 2022, 9:45pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/4 "2022-07-07T21:45:24Z")

</div>

Thank you very much, it worked!

---

<div class="post-metadata">

**Author:** ![r.castro](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@r.castro](https://forum.inductiveautomation.com/u/r.castro)\
**Post date:** [July 7, 2022, 9:45pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/5 "2022-07-07T21:45:45Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/e/3e08c92fa07b3bf8460194d3f05ac051b5c5a696.png)

---

<div class="post-metadata">

**Author:** ![kirill\_ivachkine](https://avatars.discourse-cdn.com/v4/letter/k/5f9b8f/32.png) [@kirill\_ivachkine](https://forum.inductiveautomation.com/u/kirill_ivachkine)\
**Post date:** [July 7, 2022, 9:58pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/6 "2022-07-07T21:58:20Z")

</div>

thank you for the prompt reply Castro. It’s all coming together now

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [July 7, 2022, 10:18pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/7 "2022-07-07T22:18:12Z")

</div>

Please do tag your posts as _Perspective_ or _Vision_ if relevant. The answers can be very different.

---

<div class="post-metadata">

**Author:** ![Travis.Dreier](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@Travis.Dreier](https://forum.inductiveautomation.com/u/Travis.Dreier)\
**Post date:** [January 24, 2023, 10:04pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/8 "2023-01-24T22:04:10Z")

</div>

With Vision,

I recently switched to using and active directory that our IT department manages and does not allow passwords that don't expire. Most operators of the system do not need to login or if authenticated would not have any useful roles.

Looking for ideas on how to give higher level access to features without forcing login initially.

Played a bit with authentication challenge feature that points to the new active directory while leaving the vision project properties set to the user source that has static credentials. This can work but is not and easy change to update all projects.

I really just need a do not require login check box for vision.

Any ideas?

---

<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:** [January 24, 2023, 10:09pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/9 "2023-01-24T22:09:07Z")

</div>

Use a user source that is a composite: The active directory as primary, but with a soft fallback to the internal default user source. Auto-login to the existing guest account in the default user source.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 24, 2023, 10:09pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/10 "2023-01-24T22:09:09Z")

</div>

Auto login to a generic user account in user source A. Configure user source A with 'soft' failover to user source B, which is an AD-type user source. Give A and B the same role names.  
Security setup inside the project follows the typical Vision model - lock down windows, controls, etc as necessary based on roles. Give operators the ability to easily authenticate with buttons that invoke [`system.security.switchUser`](https://docs.inductiveautomation.com/display/DOC81/system.security.switchUser).

Or, from a security/auditing mindset... don't use a generic login and retrain your operators. But I recognize the need to be more pragmatic than that a lot of the time.

---

<div class="post-metadata">

**Author:** ![Travis.Dreier](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@Travis.Dreier](https://forum.inductiveautomation.com/u/Travis.Dreier)\
**Post date:** [January 24, 2023, 10:29pm UTC](https://forum.inductiveautomation.com/t/login-disable-for-launching-application/61658/11 "2023-01-24T22:29:45Z")

</div>

@paul-griffith @pturmel Thanks that should work. These systems are also used without keyboards and in an area with lots of cameras so reducing unique password entry is preferred. Badge reader would be ideal for this.

Thanks again
