Prove time > token expired time

[alejandromartinezgotor]

when I try to generate a proof with the command:

• giza prove --framework EZKL --model-id 419 --version-id 2 --size S input.json I get the following error:
• Exception: Token expired or not set. API Key not available. Log in again. It seems that the expiration time of the token has a higher priority than the time it takes for the proof to be generated. I think it would make more sense to check if the token is expired every time the user wants to launch a command, and not at runtime.

[Gonmeso]

JWT tokens are short-lived (4 hours) so if you start a process that could take more than the time that it has left, at some point it will fail, for long lived tasks is better to use API KEYs, as JWT are short lived for security reasons.

The token validity is checked before every command that hits the API, not at runtime. For example, if you start a proving job for that we start a loop to check the status every 10 seconds, each 10 seconds an outgoing request is sent, but before sending it the token is validated, so if the proving job takes 2 hours, but you only have one hour left in the token at some point in the loop the token will be unsuable, thats why we created API keys, to deal with long tasks.

We could add for anything that could last more than X amount of time, the time left in the JWT to warn the user @alejandromartinezgotor