Triggers & Password Generator Profiles in Enforced Configuration

Summary

KeePass users have raised concerns about the decision to move triggers and password generator profiles into the enforced configuration. This discussion explores the implications of this change and potential solutions to allow users to maintain their personal triggers and profiles.

Problem Statement

The enforced configuration file is deployed to computers in a company, but this approach prevents users from customizing their own triggers and password generator profiles. This can lead to difficulties in maintaining password generator templates for different websites.

Current Solution

According to Dominik Reichl, users can mix enforced and non-enforced triggers by adding a MergeContentMode="Merge" attribute to the /Configuration/Application/TriggerSystem element in the enforced configuration file. Users without administrator privileges can then add their own triggers to their local configuration file using an XML/text editor.

Alternative Solution

Bryan Curnutt suggests a solution where the password generator dialog allows users to transfer their password templates to a new "enforced" configuration file. In this way, users can maintain their custom password templates without having to access the enforced configuration file.

Password Generator Profiles

Wellread1 recommends developing a strong password generator profile that meets the requirements of most websites, including at least one uppercase letter, one lowercase letter, one digit, and one special character. This approach can simplify password generation and reduce the need for manual tweaks.

Special Characters

However, web sites have varying definitions of what constitutes a "special character". Wellread1 suggests using special characters sparingly and selecting one special character that satisfies most websites, including it only once in the password.

Triggers

Gilles Pion suggests a better approach to allow end-user to edit its own personal triggers using the GUI, using an option in the trigger edit form.

Conclusion

The discussion highlights the need for a balance between enforcing a company-wide configuration and allowing individual users to customize their environment. The solutions proposed by the community can help address these needs and improve the usability of KeePass.

Code

The solution involves modifying the KeePass executable to allow users to add their personal triggers to the local configuration file, alongside the enforced configuration file.

Discussion

• KeePass GitHub Issue