Skip to content
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

Programmatically get authorization code #26

Open
mNemlaghi opened this issue Jul 21, 2021 · 8 comments
Open

Programmatically get authorization code #26

mNemlaghi opened this issue Jul 21, 2021 · 8 comments

Comments

@mNemlaghi
Copy link

Hi,

As mentioned here, it seems not possible to automate the way we can get authorization code, before getting access token and refresh token (which is taken into account thanks to get_bearer_token method). This is an issue for browserless, server side solutions interacting with intuit quickbooks API.

Since the refresh token doesn't last more than 1 day (the 100 days was never guaranteed), is there a planned solution for this ? Thanks a lot !

@dantebarba
Copy link

@mNemlaghi did you find a solution to this?

@daccorti
Copy link

daccorti commented Apr 27, 2022

@mNemlaghi Also interested if you solved this issue.

@IntuitDeveloperRelations - Do you have any recommendations for this?

@bdsoha
Copy link
Contributor

bdsoha commented Jul 20, 2022

@mNemlaghi Any updates? This would be a great feature for server-side applications and lambda-functions.

@An4ik
Copy link

An4ik commented Jan 10, 2023

We've faced the same issue but did some tricks to solve it:

  1. Using OAuth2 fetch the token manually
  2. Store refresh token in environment
  3. Use that refresh_token and refresh it for every request to QuickBooks API.

So based on documentation documentaion hope this will work

Refresh tokens
Refresh tokens are valid for 100 days. This expiry date is rolling and gets extended each time it’s used to refresh an access token.

@Donny-GUI
Copy link

i ended up just using selenium headless

@aaldaghar
Copy link

Is there no plan to fix the authorization code issue?

@dantebarba
Copy link

We've been using the refresh token with no issues but we only have one instance. If you scale to multiple instances or you use lambda functions unfortunately the only way to handle this without requiring scraping the QB webapp is to have a distributed database with the valid refresh token and an atomic control on the token access and renewal.

@bdsoha
Copy link
Contributor

bdsoha commented Jul 5, 2023

i ended up just using selenium headless

Do you mind sharing the code you used?

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

No branches or pull requests

7 participants