highpost
(Daniel Sears)
September 12, 2020, 12:32am
1
I’m using the git-credential-libsecret
credential helper and it’s working fine. But I can’t manage these credentials with seahorse
. When I change a git credential (personal access token) the new credential takes effect, but I can’t see any of this in seahorse
or see a related file in .local/share/keyrings. Is this expected?
Thanks.
1 Like
rschupp
(Roderich Schupp)
September 14, 2020, 2:47pm
2
I just generated a personal access token on gitlab.gnome.org (with name “patsy”), added
[credential]
helper = libsecret
in my local .git/config
, then did “git push”, was prompted
Username for 'https://gitlab.gnome.org': patsy
Password for 'https://patsy@gitlab.gnome.org': <token>
and now it shows, e.g. with secret-tool
$ secret-tool search user patsy
[/org/freedesktop/secrets/collection/login/106]
label = Git: https://gitlab.gnome.org/
secret = <token>
created = 2020-09-14 14:20:46
modified = 2020-09-14 14:20:46
schema = org.gnome.keyring.NetworkPassword
attribute.protocol = https
attribute.user = patsy
attribute.server = gitlab.gnome.org
or in Seahorse
2 Likes
highpost
(Daniel Sears)
September 17, 2020, 8:45pm
3
Yes, this is pilot error. Sorry for the trouble.
1 Like
system
(system)
Closed
October 1, 2020, 8:45pm
4
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.