`glab auth status` gives incorrect information about token validity for non-token authentication flows
Checklist
-
I'm using the latest version of the extension (Run glab --version)- Extension version: glab version 1.25.3-59
-
Operating system and version: Put your version here -
Gitlab.com or self-managed instance? both -
GitLab version (if self-managed) master (Use the versionendpoint, like this: gitlab.my-company.com/api/v4/version) -
I have performed glab auth statusto check for authentication issues
Summary
When a user triggers glab auth status after having authenticated via any flow that is not "Token", the information provided about validity of token is incorrect.
Edited by Marcel van Remmerden