Add support for customizable entry layouts

[gagarine]

I'm using https://play.google.com/store/apps/details?id=keepass2android.keepass2android&hl=en on android (sync via dropbox).

Keepass2android let me add entry using template (Standard entry, Credit Card, Secure Note, ...). Those template are recognized by keepassxc for added entry and are listed in the folder "template", but I can't use them to create a new entry from keepassxc.

[droidmonkey]

Nice suggestion. What benefits do the templates give?

[gagarine]

Template are a feature of keepass DB that let you quickly use custom field when you create a new entry: http://keepass.info/help/v2/dbsettings.html#templates

Keepass2android add some default template for you and then let you choose witch template to use when you add a new entry: Standard:

Custom secure note:

Credit cart:

[droidmonkey]

I see, so it just populates attribute fields, but with a fancy gui presentation. Not a bad idea!

[gagarine]

Exactly :). Template are stored in the /template folder in the database. So in my opinion their is two features:

• be able to create new entry based on template stored in the template folder, and propose a fancy GUI for the attributes fields ;).
• add some "default" template in this folder. In the android application this function is in the settings "create default templates".

[andyleejordan]

I just switched over from LastPass to KeePassXC (having using KeePass many years ago), and would love to have templates again. I have a lot that migrated into plain entries with the notes field populated, so I have the info, but it's not very pretty.

[ckotte]

I would like to switch from 1Password to KeePassXC (and Keepass2Android), but unfortunately there are some nice features missing like multiple URLs, custom attributes/templates used across different implementations (i.e. KeePassXC, Keepass2Android, and Tusk browser add-on), or custom attributes in main view.

This feature as well as #1177 would make KeePassXC more advanced like 1Password or LastPass. Are there any news about a possible implementation?

[droidmonkey]

Some features you mention are limited by the KeePass standard (multiple URL's for one). Also, we do not control any other project's implementations (KeePass2Android/Tusk/etc). There are plans, but everything takes time/people/etc.

[ckotte]

Some features you mention are limited by the KeePass standard (multiple URL's for one). Also, we do not control any other project's implementations (KeePass2Android/Tusk/etc).

Is the KeePass 2.x version for Windows the current "KeePass standard"? I assume you will likely implement new features introduced in this version instead of introducing features that break the "KeePass standard", right?

It would be nice if there could be some kind of coordinated improvement across all the different implementations to have a more common "feature set" across different platforms..

[boweeb]

FWIW, at least KeeWeb, MacPass, KyPass, and even KeePass 2.x itself all implement the "Templates" group pattern. They basically all work the same as @gagarine described in keepass2android except for the creation of default templates (which I think is a neat idea).

[TheZ3ro]

Can someone link/post an example of a template's code?

[phoerious]

It's just a meta data element that says which group contains the templates. It's shortly described in our new KeePass2 XML spec https://github.com/keepassxreboot/keepassxc-specs/blob/master/kdbx-xml/rfc.txt

[TheZ3ro]

I know about that metadata key and the group.

A template is a normal KeePass entry with all required data already entered.

This is what I was asking :laughing:

[ghost]

Well +1 for this whenever it drops, sadly back to vanilla KeePass that already has the functionality via a plugin. I imagine EPIC means in a couple years perhaps? Haven't taken a look at a roadmap if any, so just assuming.

What baffles me is if KeePass from the ground was never intended as an alternative to commercial apps? Because to me it seems obvious you wanna store Credit Cards, Router, Bank Account info etc and not all of those conform to "user, password, url" schema. And the top commercial apps have had this for years now. Which is when I migrated my info from 1Password to KeePass 2.x I was baffled to have so many fields gone or in short categories like Credit Cards completely unusable.

[navin09]

+1

I'm missing this feature from Keepass.

[droidmonkey]

This is my next major effort.

[adelphi23]

Newbie here, so apologies in advance if this has been addressed already. I'm trying to migrate from 1password to keepassxc, so I am facing the same issues raised above bey TehPsychdelic and others. In my case, I am moving my 1200+ entries manually and want to avoid having to do double work. As of Nov/18, Is it possible to create and/or import templates? I started creating my own templates based on 1Password fields, but am afraid that after all the work I would find out that a set of standard templates was implemented and/or will be implemented. An alternative would be to import templates from keepass, but I don't know whether this is feasible and whether keepassxc will keep that template set instead of creating a new one. Any hint would be mostly welcome.

[droidmonkey]

No form of templates is currently supported by KeePassXC.

[adelphi23]

Thanks for the prompt reply!

[MichaelYochpaz]

Any plans of adding templates soon? Would be very usefull

[droidmonkey]

Slated for 2.5

[CueHD]

While not ideal, you could perform your migration from 1Password, etc. to a Keepass database using another implementation that does allow for templates then open and use KeepassXC after then. Since the migration is a one time event, this can be a temporary workaround. As is it likely that you will need at least a second implementation to use your database on a mobile device anyway, that could be a good starting point.

[adelphi23]

Thanks! That's very useful. Would you recommend any Keepass database implementation that allows for templates? I would assume that when KeepassXC gets support for templates it should keep compatibility with the database.

[CueHD]

I migrated from Norton to KeepassXC and did not have any entries with extra fields at the time. Since then, I have used the template feature in Keepass2Android to create entries that use them. So, I do not have experience in what would be best for your migration. Other comments mentioned KeeWeb, MacPass, KyPass, and KeePass with a plugin.

[CueHD]

I would like to switch from 1Password to KeePassXC (and Keepass2Android), but unfortunately there are some nice features missing like multiple URLs, custom attributes/templates used across different implementations (i.e. KeePassXC, Keepass2Android, and Tusk browser add-on), or custom attributes in main view.

This feature as well as #1177 would make KeePassXC more advanced like 1Password or LastPass. Are there any news about a possible implementation?

You can use multiple URLs. Often, I have added a URL while using Keepass2Android since the mobile site sometimes differs from the main site and the appropriate URL is added to the entry. Keepass2Android also adds a URL field when associating the entry with an APP. These fields are found in the Advanced part of an entry in KeepassXC.

[yan12125]

I played the template feature in Keepass2Android for a while. Here's a sample file: https://dl.chyen.cc/test.kdbx (password 123) https://dl.chyen.cc/test.xml (the same database, extracted XML).

For entries created from templates, a custom field _etm_template_uuid stores the uuid (in hex) of the source template. In a source template entry, there are three fields for a custom template field, _etm_title_XXX, _etm_type_XXX and _etm_position_XXX.

Those keywords do not appear in KeePass source code [1]. Instead, they are apparently first introduced in this plugin: https://github.com/mitchcapper/KPEntryTemplates [2][3].

[1] https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.41/KeePass-2.41-Source.zip/download [2] https://github.com/mitchcapper/KPEntryTemplates/commit/83ca314cf1d15a96fb62e4880beb88273a2f007d [3] https://github.com/PhilippC/keepass2android/commit/5d8aa8afe098c428b7014185d326cbfe2dc18fae

[droidmonkey]

Great job sleuthing!

[Lantizia]

So (for those of us mostly interested in this for multiple URL support) does this mean we can have attributes... K2PA_URL_1 K2PA_URL_2 K2PA_URL_3 K2PA_URL_4 and so on...

This is how Keepass2Android does it (I'm also someone who uses this on database files where I'm using KeePassXC on desktops) to store both general URLs and also androidapp:// URLs for autocomplete on apps.

If KeePassXC does start to support these attributes (without needing to dig around in Advanced) then KeePassXC-Browser will need to look for these URL possibilities too.

But I'm not sure if these are related to templates?

[trymeouteh]

This will help make your account fields more organised. Many accounts these days will ask for not just a username but a email address and a phone number.

[tunbridgep]

I also support this. The KeePassTemplates plugin (which KeepassAndroid integrates/supports) was extremely useful for organisation.

[OLLI-S]

I tested LastPass some months ago and here I can select the “Type” of secure note (secure note is an entry that is not a password entry). Each Type has predefined fields that I can fill (I do not have to add these fields manually).

Here some examples what types are available in LastPass:

• software licences
• email accounts
• bank accounts
• servers
• WIFI passwords
• smartphone
• (many other types)

Please also add templates, where I have some predefined fields that I can fill.

Here are some screen shots of LastPass.

Select the type of secure note:

Email Account:

Software License:

Bank Account:

WIFI-Password:

I also found a list of fields that a user posted in the Bitwarden community: https://community.bitwarden.com/t/add-more-pre-defined-item-types/228/3

This list is very complete.