Make a proper GUI for adding Reference to standard fields

[flyinbutrs]

I'm not sure if this is already supported or if this is a feature request, but is there a way to create / utilize references like described here for Windows keepass2?

[TheZ3ro]

Currently there isn't a nice GUI for inserting references beside when duplicating/cloning an entry. (Like https://superuser.com/a/434046) But if you manually insert the reference code and KeePassXC will interpret the reference correctly

[flyinbutrs]

Could you elaborate on how to do that exactly? What would I put as the password in entry A to reference the password for entry B?

[TheZ3ro]

@flyinbutrs Yes, the complete reference format is described on KeePass website.

Currently you will need to build KeePassXC form source from the develop branch and the only way to link references is by using entry UUID.

So if you want to do this right now you have to:

• Go in the entry you want to reference and from the Property section copy the UUID
• Create a new entry
• Set the attribute you want to reference to {REF:<WantedField>@I:<UUID>} and pasting the UUID.

WantedField can only be a standard field:

T   Title
U   User name
P   Password
A   URL
N   Notes

Later I will add this to the wiki maybe

[flyinbutrs]

Not discounting user error, but I don't think this is working. I put this into a password field (twice):

{REF:P@I:77d14b5fb035281bc4d2781e006cf386}

And have double checked that the UUID is correctly pointing to another entry, but when I go to the page, both keepasshttp, autotype, and command+c put that exact string into the password field / clipboard rather than the referenced password.

I'm using keepassxc 2.1.3 on OSX, if it matters.

[phoerious]

2.1.3 doesn't support references yet. You need to compile the develop branch for that. Relevant PR: #370

[flyinbutrs]

Oops... reading comprehension failure. Is that coming in the next release? I'd prefer not to compile from source if it's only going to be a few weeks.

[phoerious]

We don't have a release date yet and some major features are yet to be completed.

[Felixoid]

Hi, any progress here?

What about to add submenu Copy reference to clipboard here?

[lagagain]

@Felixoid I like the function in keepass2, and add to submenu is a good idea, but in my use cases, frequently, are that need add a account which use OAuth login(like login with google, facebook or github). Because that, I don't think the way(just add to submenu) is very sense to me.

[zioalex]

Hi Guys, any update here. This feature is very convinient and I miss it coming from KeePass.

[ftorto]

Isn't it a duplicate of #2030 ?

[Felixoid]

Looks like otherwise, @ftorto

[mcflypl]

I use AD login on many pages and I miss this feature...

[stefan123t]

@flyinbutrs I like your idea :+1: of having several (if not all) Field Reference Entries available to insert at the current cursor position / at the end of the Use custom Auto-Type sequence: Input field. while it could even be extended to have some {COMMAND} completion as suggested in #6782 and #6462 :innocent:

Configuring Auto-Type Sequence in the dialog usually requires reading the documentation sections under Configure Auto-Type Sequences and Searching the Database

The dialog still has plenty of space under the [ ] use a specific sequence for this association input box to at least add those two documentation links and place some insert buttons for the feature requested here:

The most frequently used / known ones are IMHO as they are also supported in KeePass, KeePassX and KeePassXC: Field Reference / Placeholders	Description
{USERNAME}{TAB}{PASSWORD}{ENTER}	Default (Username & Password)
{USERNAME}	Username
{TAB}	Tab
{PASSWORD}	Password
{ENTER}	Enter
{TOTP}	Current TOTP
{DELAY 2500}	Delay of 2500 ms
{CLEARFIELD}	Clear the current Input field
{S:<ATTR_NAME>}	Additional Attribute ATTR_NAME
{REF:U@I:<UUID>}	Username of another Entry UUID
{REF:P@I:<UUID>}	Password of another Entry UUID
{REF:<FIELD>@<SEARCH_IN>:<SEARCH_TEXT>}	FIELD from another Entry with Field SEARCH_IN matching SEARCH_TEXT

• ATTR_NAME should be a pull-down offering all the configured Additional Attributes of the Entry, regardless whether Protected or not.

• FIELD and SEARCH_IN should be pull down boxes offering the following Options:

Fields	Name
T	Title
U	User name
P	Password
A	URL
N	Notes
I	UUID
O	Other custom strings (KeePass 2.x only)

• UUID or SEARCH_TEXT should allow to using an ... Ellipsis Button to select / search one of the entries from the Database in a separate dialog and select its Name, UUID, etc. as value. There could be further hints to the Regex Options in the UUID / SEARCH_TEXT Field as documented under

Modifiers	Description
-	Exclude this term from results
!	Exclude this term from results
+	Match this term exactly
*	Term is handled as a regular expression

Wild Card Character	Description
*	Match anything
?	Match one character
\|	Logical OR

Sample Search Query	Description
user:johnsmith url:www.google.com	Searches the Username field for johnsmith and the URL field for www.google.com.
user:john\|smith	Searches the Username field for john OR smith.
+user:johnsmith -url:www.google.com *notes:"secret note \d"	Search the username field for exactly johnsmith, the URL must not contain www.google.com, and notes contains secret note [digit].

[yaoyingkeji]

Export file (xml、html、csv), reference location, not reference content, but code?

[yaoyingkeji]

Using "{REF:T@I:c634a207451b4643ac8daf8ef44f40cb}" in Additional attributes has no effect.