To make things slightly worse, it looks like an API key that is manually “un-revoked” will be revoked again the next day if it is not also *actually used*. So the 30 days are evaluated every day based on time since the last API call, and “un-revoking” the key does not count as using it. On Wed, Feb 22, 2023, at 10:56 AM, Ben Beasley wrote: > Am I missing something, or does this basically break ABRT for users, > since that has required an API key rather than a username and password > for some time, and it’s not usual to report bugs with ABRT even as > often as once a month? It doesn’t seem reasonable to have to go > manually reset an API key every time I want to report a bug, and I’m > concerned that this will reduce the number of useful crash reports we > get. > > On Wed, Feb 22, 2023, at 10:46 AM, Ben Cotton wrote: >> If you did not see the bugzilla-announce-list post[1], there are new >> requirements for API keys in Red Hat Bugzilla: >> >> Red Hat Bugzilla has introduced a 12 month lifetimes for API keys. You >> must replace your API keys at least once a year. Additionally, any API >> key that is not used for 30 days will be suspended but can be >> re-enabled on the account's preferences tab. >> >> All existing API keys have had their creation date set to 2023-02-19. >> For more details, see the announcement[1]. >> >> [1] >> https://listman.redhat.com/archives/bugzilla-announce-list/2023-February/000101.html >> >> -- >> Ben Cotton >> He / Him / His >> Fedora Program Manager >> Red Hat >> TZ=America/Indiana/Indianapolis >> _______________________________________________ >> devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to >> devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> _______________________________________________ >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
