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

Quickbooks Online Linked Service - Need more information on how refresh tokens are handled #122219

Open
rgknight opened this issue May 3, 2024 · 3 comments

Comments

@rgknight
Copy link

rgknight commented May 3, 2024

We are using the Quickbooks Online Linked Service, described here: https://learn.microsoft.com/en-us/azure/data-factory/connector-quickbooks?tabs=data-factory

The copy data service doesn't ask for Access Tokens. It must therefore be using the refresh token to request a new access token.

When you refresh the access token, QBO will periodically update the refresh token, invalidating the previous refresh token. See: https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/faq
image

It is unclear from the documentation how the Linked Service handles the new refresh token. If you are using a secret from the Azure Key Vault, does it update the value to the latest refresh token?

If it does nothing with the new refresh token -- not even returning it as an output, this is a bug.

If it updates the refresh token value, the documentation needs to be updated to explain this.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@GKFFgithub
Copy link

Information on the page:

Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@PesalaPavan
Copy link
Contributor

@rgknight
Thanks for your feedback! We will investigate and update as appropriate.

@TPavanBalaji
Copy link

@rgknight
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.

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

No branches or pull requests

5 participants