Skip to content

Support using Personal Access Tokens instead of plain text password storing #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
G-Rath opened this issue Jul 8, 2019 · 3 comments
Labels

Comments

@G-Rath
Copy link

G-Rath commented Jul 8, 2019

This should also solve #94

https://help.getharvest.com/api-v2/authentication-api/authentication/authentication/

@zenhob zenhob added the feature label Nov 4, 2019
@mkarnicki
Copy link

I don't think it will resolve #94 - I created a personal access token on an account within an org that has Google Login enabled - I can only access my user info via the API, all other endpoints return HTTP 403.

@fwolfst
Copy link

fwolfst commented Jan 31, 2022

I don't think it will resolve #94 - I created a personal access token on an account within an org that has Google Login enabled - I can only access my user info via the API, all other endpoints return HTTP 403.

Pretty sure I have another experience, but will have to evaluate. Plaintext password is a no-go here unfortunately, too.

@fwolfst
Copy link

fwolfst commented Jan 31, 2022

Unfortunately personal (non-oauth) access tokens are not supported in v1 of the harvest API that is used by this gem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants