parsing authentication shows confusing error

[migmartri]

For example

chainloop att init --name testing --project new-project  --replace --version 1.2
Flag --name has been deprecated, please use --workflow instead
This command is will run against the organization "miguel-test"
Please confirm to continue y/N
y
ERR failed to load issuer: authorization error: issuer not found: cp.chainloop

this should have shown that the token is expired.#2443

[Piskoo]

I've managed to replicate it 1.43.0

ERR failed to load issuer: authorization error: issuer not found: cp.chainloop
$ chainloop version
Client Version: 1.43.0
Server Version: 1.45.3

But seems to be fixed in 1.45.3

ERR rpc error: code = Unauthenticated desc = couldn't match JWT provider: error: code = 401 reason = UNAUTHORIZED message = JWT token has expired metadata = map[] cause = <nil>

[jiparis]

I confirm that the error is the right one, but I think we should do something with the message. The current error message is awful and not user-friendly at all. It also doesn't give any clue about mitigation actions.

[migmartri]

I do not think this is fixed, before the error was handled here I think, not anymore

chainloop/app/cli/main.go

Lines 87 to 88 in 9cdafe7

	case isWrappedErr(st, jwtMiddleware.ErrTokenExpired):
	msg = "your authentication token has expired, please run chainloop auth login again"

[migmartri]

I think this problem is not a regression, is the fact that we handle errors differently depending on the operation that you are doing (attestation process or something else)

For example, doing a regular operation it works as expected

go run main.go wf ls
ERR your authentication token has expired, please run chainloop auth login again
exit status 1

but doing an attestation using local authentication does not

go run main.go att init --workflow test --project bar
This command is will run against the organization "chainloop"
Please confirm to continue y/N
y
ERR failed to load issuer: authorization error: issuer not found: cp.chainloop
exit status 1