Add CLI user commands

[ThomasLaPiana]

Closes #2136

Code Changes

• add a fides user login CLI command (uses user endpoint, not client endpoint)
  • add logic for getting an access_token from the webserver with a username/password or with an existing credentials file
  • add logic for storing the access_token and the username in a .fides_credentials file in the user directory
  • Base64 encode the password before sending it
• add a fides user create command for creating a user
• add a fides user permissions command for showing the scopes of the current user
• add tests for all of the above
• use matching username/password options for commands that require it (login and create, for example)
• allow for credentials file path override via env var

Relevant Links:

• oauth docs

Steps to Confirm

• make sure the webserver is available when running your commands
• run fides db reset -y to clear the database of any existing users
• run fides user login -u root_user -p Testpassword1! and verify a credentials file is written with the correct info
• run fides user login and verify that you're prompted for the username and password, and that the password is hidden
• run fides user login -u fidesadmin -p wrongpassword and verify the error message
• run fides user create newuser HolyCow1*1 and confirm that a new user is created
• run fides user login -u newuser -p HolyCow1*1 and confirm that the login is successful and the credentials file is updated
• run fides user permissions and verify that the permissions are correct (all permissions)
• set the FIDES_CREDENTIALS_PATH env var and confirm that is respected as the path for the credentials file

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation:
  • documentation complete, PR opened in fidesdocs
  • documentation issue created in fidesdocs
• Issue Requirements are Met
• Relevant Follow-Up Issues Created (Add authentication to all unauthenticated API endpoints #2165 )
• Update CHANGELOG.md

Description Of Changes

This PR adds a user command group to the CLI that allows the CLI to authenticate with the webserver and store the username, password, access_token and id in a local .fides_credentials file

[ThomasLaPiana]

Bug Found: root client can't get their own scopes

[ThomasLaPiana]

Potential bug found: I created a new user but when I search for that user, the search turns up empty

[ThomasLaPiana]

@sanders41 do you think I should be using clients or users here? I'm thinking users is what we actually want, since clients are ephemeral API users created by actual users right?

[sanders41]

@sanders41 do you think I should be using clients or users here? I'm thinking users is what we actually want, since clients are ephemeral API users created by actual users right?

Right, I would use users

[ThomasLaPiana]

running into a perplexing error:

fides> fides user create newusera Newpass!word1
Loading config from: .fides/fides.toml
{'username': 'newusera', 'password': 'Newpass!word1'}
{ 'detail': [ { 'loc': ['body', 'password'],
                'msg': "'utf-8' codec can't decode byte 0xec in position 1: "
                       'invalid continuation byte',
                'type': 'value_error.unicodedecode'}]}

Trying to create a new user via the API and I am getting this error about the password, but it doesn't happen when using the Swagger docs so it must be something with the way I'm sending the request....

[ThomasLaPiana]

running into a perplexing error:

fides> fides user create newusera Newpass!word1
Loading config from: .fides/fides.toml
{'username': 'newusera', 'password': 'Newpass!word1'}
{ 'detail': [ { 'loc': ['body', 'password'],
                'msg': "'utf-8' codec can't decode byte 0xec in position 1: "
                       'invalid continuation byte',
                'type': 'value_error.unicodedecode'}]}

Trying to create a new user via the API and I am getting this error about the password, but it doesn't happen when using the Swagger docs so it must be something with the way I'm sending the request....

@sanders41 I confirmed that that password specifically was causing the issue, if I make the same call with HolyCow1*1 it works perfectly.

Any idea why? What is weird about Newpassword1!?

[sanders41]

I’m on my phone instead of computer at the moment so I can’t test this, but I think the issue, may be that the endpoint expects to receive the password as a base64 encoded string (see here). So I am thinking maybe it can decode HolyCow1*1 as if it was base64 encoded but not Newpassword1!

[ThomasLaPiana]

I’m on my phone instead of computer at the moment so I can’t test this, but I think the issue, may be that the endpoint expects to receive the password as a base64 encoded string (see here). So I am thinking maybe it can decode HolyCow1*1 as if it was base64 encoded but not Newpassword1!

Ah I see......that'd do it

[ThomasLaPiana]

New login flow:

No options provided

fides> fides user login
Loading config from: .fides/fides.toml
Username: root_user
Password: 
Logged in as user: root_user
Credentials file written to: C:\Users\tlapiana/.fides_credentials

Username provided only

fides> fides user login -u root_user
Loading config from: .fides/fides.toml
Password: 
Logged in as user: root_user
Credentials file written to: C:\Users\tlapiana/.fides_credentials

Password provided only

fides> fides user login -p Testpassword1!
Loading config from: .fides/fides.toml
Username: root_user
Logged in as user: root_user
Credentials file written to: C:\Users\tlapiana/.fides_credentials