Forum Discussion
Custom data connector using oauth2 not refreshing access token
Microsoft updated a page to say that oauth2 tokens expire after an hour in the gateway.
This is buggy behavior. And it is very different than what we experience in the PBI desktop. Ideally the enterprise gateway would work better than the PBI desktop, rather than worse.
Based on the inspection of the underlying code, the AAD tokens are supposed to be refreshed. I'm not sure why there is so much friction going on between a popular Microsoft product, and the Microsoft AAD identities.
Two years later, and there is very little progress. I did notice a comment that says dataflows may not suffer the same problems as datasets:
"
Dataflows specifically were recently updated to support token refresh, so they are no longer subject to the 1 hour timeout. However, other artifacts, such as pipelines, copy jobs, or semantic models, are still subject to the limitation."
... Unfortunately the reason dataflows aren't a good option, is because we can't use them with custom connectors. There is no support for custom connectors in dataflows. That incompatibility has been in place for many years, and Microsoft keeps pushing out their promised ETA. I believe the current ETA is end of 2025.