# Mobile app does not clear username password on exit

**URL:** <https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644>\
**Category:** Ignition\
**Created:** [April 9, 2018, 5:38pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644 "2018-04-09T17:38:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwaynesmith](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@mwaynesmith](https://forum.inductiveautomation.com/u/mwaynesmith)\
**Post date:** [April 9, 2018, 5:38pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/1 "2018-04-09T17:38:34Z")

</div>

We have noticed that the mobile app does not clear username password on exit. therefore, when the user reenters the app (or another user picks up the same unit) the username/password is still populated. We would like it cleared on exit?

---

<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:** [April 9, 2018, 7:56pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/2 "2018-04-09T19:56:17Z")

</div>

It’s your browser that is storing the username and password (just like any other username and password field on any other website).

We are already including `autocomplete=off` attributes on the elements, so we’ll have to look into whether there’s more we can do to try and tell browsers not to allow saving the values.

---

<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:** [April 9, 2018, 8:03pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/3 "2018-04-09T20:03:38Z")

</div>

> [@Kevin.Herron](#):
>
> We are already including autocomplete=off attributes on the elements, so we'll have to look into whether there's more we can do to try and tell browsers not to allow saving the values.

Ewww!  
That's really unfriendly to [modern password best practices](https://www.schneier.com/blog/archives/2017/10/changes_in_pass.html) -- namely, to use a password manager so one only has to remember the password manager's encryption passphrase.

---

<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:** [April 9, 2018, 8:16pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/4 "2018-04-09T20:16:19Z")

</div>

> [@pturmel](#):
>
> Ewww!That's really unfriendly to modern password best practices -- namely, to use a password manager so one only has to remember the password manager's encryption passphrase.

Yeah, it's tricky. I agree with you about using password managers, but imagine any kind of shared workstation or tablet or even a phone that isn't shared but someone gets their hands on it - should a stranger be able to log in to your HMI project because an operator wasn't trained not to save the password when every browser out there will ask you to save it?

---

<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:** [April 9, 2018, 8:29pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/5 "2018-04-09T20:29:32Z")

</div>

Any shared workstation should be using a native client launcher – no browser at all. I would argue that the mobile module is unsecurable for shared use – for precisely the reason you point out. Mobile devices are made for sole users – architected that way through and through – and cannot be made secure for multiples.

---

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [April 9, 2018, 8:42pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/6 "2018-04-09T20:42:21Z")

</div>

I thought at least android supports multiple user accounts?

Granted I’ve never had to use it…

---

<div class="post-metadata">

**Author:** ![magno32](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/magno32/32/3402_2.png) [@magno32](https://forum.inductiveautomation.com/u/magno32)\
**Post date:** [April 9, 2018, 8:57pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/7 "2018-04-09T20:57:05Z")

</div>

Thanks for your response.

I don’t really think this is the issue (demonstration below, in private mode on Firefox). Is it possible that the underlying Java client is not clearing the fields when the exit/logout button is pressed?

FWIW, we have password storage disabled on the devices browser (again, I think this issue is unrelated).

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/5ca10f6d2288b9c40bb9de4a0bc8e532196772fc.gif)

---

<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:** [April 9, 2018, 10:03pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/8 "2018-04-09T22:03:47Z")

</div>

This does look like something else - we’ll look into it.

---

<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:** [April 9, 2018, 10:26pm UTC](https://forum.inductiveautomation.com/t/mobile-app-does-not-clear-username-password-on-exit/17644/9 "2018-04-09T22:26:10Z")

</div>

> [@bfuson](#):
>
> I thought at least android supports multiple user accounts?

I remember it being announced, and being default disabled. I just played with my Nexus 6P and though it doesn't show user management where it is supposed to, a long-press on the admin user (me) in Settings popped up another menu. And lo, there's the Add User option. So it is possible, at least on selected devices.
