# Password Manager Integration for Classic Auth

**URL:** <https://forum.inductiveautomation.com/t/password-manager-integration-for-classic-auth/111617>\
**Category:** Ignition\
**Tags:** vision, designer\
**Created:** [October 21, 2025, 1:55pm UTC](https://forum.inductiveautomation.com/t/password-manager-integration-for-classic-auth/111617 "2025-10-21T13:55:17Z")\
**Posts on this page:** 3\
**Page:** 1

<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:** [October 21, 2025, 1:55pm UTC](https://forum.inductiveautomation.com/t/password-manager-integration-for-classic-auth/111617/1 "2025-10-21T13:55:17Z")

</div>

Discussed some time ago over here:

> [@Saving login credentials in designer](https://forum.inductiveautomation.com/t/saving-login-credentials-in-designer/27264/6):
>
> Password managers are already usable with like one extra step beyond full integration: invoke your PW manager shortcut, type in enough to get this entry to show up, then copy the password. If you have a complex username as well I guess that’s pretty annoying. I have no idea how integration with a password manager can be done from Java.

I recently stumbled across this:

> **[GitHub - purejava/keepassxc-proxy-access: A Java library to access KeePassXC via its...](https://github.com/purejava/keepassxc-proxy-access)**
>
> A Java library to access KeePassXC via its build-in proxy

(Note the MIT license.)

I added to this feature request:

> **[Improving user login to work automatically with a password manager | Ignition...](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/improving-user-login-to-work-automatically-with-a-password-manager)**
>
> Currently there doesn't appear to be a way to login to an Ignition application using a password manager lastpass, onelogin, keeper etc.

Please up vote this!

---

<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:** [October 21, 2025, 3:43pm UTC](https://forum.inductiveautomation.com/t/password-manager-integration-for-classic-auth/111617/2 "2025-10-21T15:43:47Z")

</div>

I would personally rather see some kind of extension point within the login process to allow modules to provide their own hooks than first party integration with a single 'blessed' protocol, though Keepass is definitely a good choice if we did go that way.

---

<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:** [October 21, 2025, 3:50pm UTC](https://forum.inductiveautomation.com/t/password-manager-integration-for-classic-auth/111617/3 "2025-10-21T15:50:56Z")

</div>

> [@paul-griffith](#):
>
> rather see

Why not both? SDK hooks **and** first implementation as first-party?