-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot choose from multiple credentials #3
Comments
I tried to ask for a choice from stdin but Git doesn't seem to allow passing user input onto helpers after it's done feeding its own request. Perhaps this is not feasible atm. |
Someday soon this may become a real problem: |
@JJRcop Enable verbose logging git-credential-keepassxc/src/main.rs Lines 548 to 558 in e131992
In terms of the desktop notifications I'd like to keep them minimal. It might be nice to see this message via notification for the first time, but over the time it just becomes annoying imo. Notifications are limited to critical events and those require user intervention for now. If we had too many, a filter would be needed, which is another rabbit hole I don't want to go down into. |
hi, I've tried the KPH solution linked above and GCK seems to still be requesting access to the marked entries. I have followed the instructions exactly (KPH field return enabled in browser options, "KPH: git" field with "false" value on the relevant entry). any advice? edit: will followup with edit since it's not worth another comment - keepassxc, when not set to "remember" your login for github, will still prompt using all logins, but GCK will filter them after. in retrospect this should be obvious.. |
@atagen I'd suggest you use |
Would you consider returning the Title (or any unique identifier) of the entries in For the (modified) example of https://github.com/keepassxreboot/keepassxc-browser/blob/develop/keepassxc-protocol.md#get-logins: $ cat > ~/a.json <<"EOF"
{
"action": "get-logins",
"url": "<snip>",
"submitUrl": "<optional>",
"httpAuth": "<optional>",
"keys": [
{
"id": "<saved database identifier received from associate>",
"key": "<saved identification public key>"
},
{
"id": "<another saved database identifier received from associate>",
"key": "<saved identification public key>"
}
]
}
EOF
$ jq '.keys[] | .id' ~/a.json
"<saved database identifier received from associate>"
"<another saved database identifier received from associate>"
$ |
I am hit by this for two repositories of different organizations on Azure DevOps. I guess I can work around it with the KPH or by defining a different git group. What would solve my case in the most convenient way, is if git-credential-keepassxc would match the URL in keepassxc (exact or take the one with the longest matching path). Is this a possibility or am I overlooking something? |
What would solve my case in the most convenient way, is if
git-credential-keepassxc would match the URL in keepassxc (exact or
take the one with the longest matching path). Is this a possibility or
am I overlooking something?
git-credential-keepassxc itself doesn't do further filtering based on
URLs (like the browser extension, to avoid surprises).
At the end of the day, only users themselves know which they want to
select and how they want to select. You can combine 'get --raw' with a
custom script.
…On 10/10/24 21:14, Bart Verhagen wrote:
I am hit by this for two repositories of different organizations on Azure DevOps. I guess I can work around it with the KPH or by defining a different git group.
What would solve my case in the most convenient way, is if git-credential-keepassxc would match the URL in keepassxc (exact or take the one with the longest matching path). Is this a possibility or am I overlooking something?
—
Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCMP7YHCSUHV2VO2EHZQQ3Z2ZHO5AVCNFSM6AAAAABPWNVCHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUGY3TQNJYGU>.
You are receiving this because you commented.Message ID: ***@***.***>
--
Frederick Zhang
PGP: 8BFB EA5B 4C44 BFAC C8EC 5F93 1F92 8BE6 0D8B C11D
|
The text was updated successfully, but these errors were encountered: