#7979 Renewing my pagure API token for fedscm-admin
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by tibbs.

I've lost the ability to run fedscm-admin because my main pagure API token has expired and I don't believe I can renew it myself.

I don't know if the PDC token expires, and I don't believe there is any way for me to check it besides just trying operations (which can be problematic because the admin tool leaves things in a bad state if any single operation fails). If someone could double check that, I'd appreciate it.

I can provide a few characters from each token which I don't think would really provide useful information to an attacker, but I'll refrain from doing that just in case.


yeah, pdc tokens I don't think expire, if you have an admin one you do.

Can you tell me when the pagure.io token expired that you want to renew?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

4 years ago

I'm not sure I know how to tell. It was generated by pagure-admin and passed on to me; I don't know how to view the expiration date. I think it might have been in January or February, but maybe as early as December.

I wonder, though, if the instructions at https://pagure.io/fedscm-admin are actually still correct. Does pagure now provide me with a way to create an API key which can create a project? If I look at the non-repo-specific token page, it does imply that I can create one with those permissions. (The token I had been using is not listed on that page.) But again, given the nature of how fedscm-admin fails leaving things in a bad state, I'm reluctant to just try it out.

Ah, I misunderstood which instance you were talking about. Looks like your src.fedoraproject.org token is already renewed.

:potable_water:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata