Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1354456

Summary: warn user when API token is out of date
Product: [Community] Copr Reporter: Tomas Tomecek <ttomecek>
Component: frontendAssignee: Jakub Kadlčík <jkadlcik>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: jkadlcik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-15 10:24:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomas Tomecek 2016-07-11 11:26:09 UTC
recently I wanted to use copr-cli after a long time; I copied content of `https://copr.fedorainfracloud.org/api/` into a local file and started using copr CLI. Authentication failed. I had no idea what was wrong. After some time I realized that the token is out of date.

Would it be possible to warn user at the API page when the token presented is no longer valid? It could save time & sanity for some people.

Comment 1 Jakub Kadlčík 2016-07-15 04:32:15 UTC
Hello Tomas, thank you for the feedback.

I just tried to reproduce it and I got


$ copr buildtito --git-url ...

Something went wrong:
Error: Login invalid/expired. Please visit copr.fedoraproject.org/api to get or renew your API token.


Did you get different message? I think this one is pretty accurate.

Comment 2 Tomas Tomecek 2016-07-15 07:01:15 UTC
My was just authentication failure. I think it was fedora 22, not sure if the version of copr cli is outdated there or not.

So if this is already fixed in recent versions, we can close.

Comment 3 Jakub Kadlčík 2016-07-15 10:24:53 UTC
Ok, I am closing this. Thank you anyway.