Repository navigation
Association between repo and key #108
|
Dear all I am unable to have git-credential-keepassxc use the correct key. If I now unlock my DB and enter, say repo A, the credential manager retrieves password for repo B. I checked this trough It does not matter which repo I enter. There is always the same key. My keys are working, i.e. if i comment the credential-helper line in my config and enter the pat myself I can pull/push etc. But using the credential manager it (obviously) only works in repo B, all the others return a 403. My keys have some arbitrary title, the username, pat and the full URL of the repo as fields. Thank you for any suggenstions |
Replies: 2 comments 1 reply
|
You can write a wrapper like Even if you can give git-cred-kpxc full URLs, it will make no difference since KPXC doesn't care about URL paths. It's like the KPXC browser extension -- no matter where you see the login form in a website, it always lists all the available credentials; so does git-cred-kpxc, only that there is no way to interact with it so it just returns the first one by default. |
|
For reference, for the next poor soul that has to figure out blindly what git sends to the helper and what the helper gets from the db. |
You can write a wrapper like
git-credential-keepassxc --git-groups --unlock 3 get --raw | jq '.entries | .[] | select(...)'.Even if you can give git-cred-kpxc full URLs, it will make no difference since KPXC doesn't care about URL paths. It's like the KPXC browser extension -- no matter where you see the login form in a website, it always lists all the available credentials; so does git-cred-kpxc, only that there is no way to interact with it so it just returns the first one by default.