How to avoid re-generating Pagure API keys all the time?

[Adam Williamson]

From time to time I have to submit a ticket with 'fedpkg request-repo' or
'fedpkg request-branch', and I have feeling that I have to regenerate the API
key very often (since 2018-02-17 I have 5th key already?!).
How do you work-around this requirement to re-generate the key all the
time? Is this necessary requirement for 'fedpkg' to work if when we have
gssapi support in Fedora?

As in, do 'kinit ***@FEDORAPROJECT.ORG' or so?

Yeah, it's been like that for several months for me. At one point it
was not. I believe the ticket is meant to last for 24 hours but be
auto-renewable for up to 7 days; at some point, for me, auto-renew was
happening, for the last while it is not.

I have never had time to look into this more deeply, though, so I never
filed any bugs. I'm not sure if it depends on GNOME keyring
integration, or if the fact that my systems are *also* members of my
personal FreeIPA domain is related.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/deve

[Randy Barlow]

From time to time I have to submit a ticket with 'fedpkg request-
repo' or
'fedpkg request-branch', and I have feeling that I have to regenerate
the API
key very often (since 2018-02-17 I have 5th key already?!).

I proposed that fedpkg could manage the API token here:

https://pagure.io/fedpkg/issue/192

[Ben Rosser]

Is this necessary requirement for 'fedpkg' to work if when we have
gssapi support in Fedora?

This is something that's been annoying me too. It would be a huge
packager quality of life improvement (IMO) if we didn't have to
request pagure keys and could instead authenticate using
GSSAPI/Kerberos for all interactions with Fedora infrastructure.

Sadly, Pagure does not support GSSAPI authentication.

I actually suggested this some time ago, when the migration from
pkgdb2 first happened-- I don't *think* there was an opposition to the
idea, there just wasn't enough time or person-power to do it:
https://pagure.io/pagure/issue/2549

Ben Rosser
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org

[Richard W.M. Jones]

Post by Ben Rosser

Is this necessary requirement for 'fedpkg' to work if when we have
gssapi support in Fedora?

This is something that's been annoying me too. It would be a huge
packager quality of life improvement (IMO) if we didn't have to
request pagure keys and could instead authenticate using
GSSAPI/Kerberos for all interactions with Fedora infrastructure.

And if krb5 keys lasted longer than 8 hours or whatever short timeout
it is. 30 days would be a good starting point.

Rich.

Post by Ben Rosser
Sadly, Pagure does not support GSSAPI authentication.
I actually suggested this some time ago, when the migration from
pkgdb2 first happened-- I don't *think* there was an opposition to the
https://pagure.io/pagure/issue/2549
Ben Rosser
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/li