Fix expired tokens not refreshing & add info command to show user info

[blam23]

isTokenExpired was not properly calling the JWT parser, and as a result an error was always returned and this led the function to always return false.

New command info added that prints out the currently auth'd user's data. Also logs the User ID when calling authenticate.

Examples:

$ prvd info
Current User:
 ID:          fe6341f0-2234-4a6a-be84-41deee38c46b
 Name:        Lucas Rodriguez
 First Name:  Lucas
 Last Name:   Rodriguez
 Email:       lucas@provide.services

$ prvd authenticate
Email: <email>
Password: <pass>
2021/09/08 14:00:16 Authentication successful.
2021/09/08 14:00:16 User ID: fe6341f0-2234-4a6a-be84-41deee38c46b

[blam23]

I can split this into two different PRs if you want, one for the fix and one for the feature - not sure how you like to manage changes :)

[blam23]

Having the interface returned here be nil causes the jwt.Parse method to always fail - if we want to parse the token without verifying we need to use ParseUnverified.

[zk-bits]

Could we change the prvd command from prvd id to prvd users id

[blam23]

Could we change the prvd command from prvd id to prvd users id

Not sure users makes the most sense - we're getting the ID for whoever is logged in, not doing any sort of user management?

[blam23]

I'm not entirely sure it's right to be under users as I would imagine that's for user management (nothing to do with auth imo) but I've created commit 1fea400 that turns it to prvd users id and provides a prompt option if you do prvd users:

$ prvd users
Use the arrow keys to navigate: ↓ ↑ → ←
? What would you like to do:
  ▸ Create
    Authenticate
    Show current authorized user's ID

$ prvd users id
fe6341f0-2234-4a6a-be84-41deee38c46b

[zk-bits]

I'm not entirely sure it's right to be under users as I would imagine that's for user management (nothing to do with auth imo) but I've created commit 1fea400 that turns it to prvd users id and provides a prompt option if you do prvd users:

I can stand behind this to be honest, I think as it stands authenticate can be reached with out users, so it is a bit redundant to also have it inside of users. If we remove it from the user category, I think it would be okay to have id as a stand alone too. Maybe rename the command to user_id or potentially, current_user?

[blam23]

As per discussion and PRVD-48, I've modified this to be prvd info which shows data about the user.

[zk-bits]

should we prompt for authentication instead of error-ing out?

[blam23]

Nothing else does - this should be consistent. We can change design in a new PR for all of the auth failures if desired, but this isn't the place to do that.

[zk-bits]

One minor comment, on design, lgtm otherwise.

[zk-bits]

Please squash all commits into one before merging.

[blam23]

Please squash all commits into one before merging.

This is easily fixed by doing a "squash and merge" in GitHub - this will keep the commit history in this PR for future reference while the main branch only gets the one squashed commit.

[zk-bits]

lgtm