The following was implemented
- Added separate method for the login. This method takes the client-id and client-secret as params.
- Added method to refresh the oauth-token
Should this completly replace the basic-auth method?
- In that case I would name the method login
- Otherwise we should decide whether the oauth is the main method for this (being called login) or if basic-auth should be main
Should there be an option to provide the access-token from the application-details overview? It would probably be useful and users wouldn't need to authenticate (and specifically refresh) with the client-id and client-secret
For refreshing the token the client-id and secret need to be provided again, making that process kinda similar to the usual login. Maybe here it would be an idea to also save client and server id in the keyring and refresh automatically on auth-errors.
The docs need to be updated for this
There are no unit-tests for this functionality yet