bitbucket OAuth

[mathstuf]

Should probably use OAuth as well.

[ryneeverett]

I looked into implementing this, but was disappointed at what I found:

• Bitbucket's OAuth2 implementation requires basic authentication to get a temporary token.
• Bitbucket's OAuth1 implementation requires browser login to get a temporary token.

My primary motivation to implement this was to avoid needing to provide bugwarrior a password, but OAuth2 doesn't solve that. And web browser login on every bugwarrior-pull is obviously not an option.

[ryneeverett]

For future reference though, requests_oauthlib has a Bitbucket OAuth1 tutorial.

[ryneeverett]

I knew I had to be wrong about this so I kept digging. You can get a refresh token:

Most access token grant response therefore include a refresh token that can then be used to generate a new access token, without the need for end user participation

So I guess we could prompt for a password on first usage and thereafter use the refresh token.

[ryneeverett]

Bugwarrior doesn't seem to persist any data of its own currently, so I think we'd need to add a ~/.task/bugwarrior.data file to store the refresh token, per the third-party guidelines:

If you need to store additional data, consider putting your own data file in the ~/.task directory. Just don't use the file names pending.data, completed.data, backlog.data, or undo.data.