Forum Discussion
Advocate IScheduled refreshes for OAuth2 authenticated datasources
What is recommendation for handling scheduled refreshes on Datasets/Dataflows when you are using OAuth2 credentials to connect to a datasource?
It seems that once the access token expires, then the scheduled refresh will no longer work - and there is no way to provide a refresh token as part of the credentials.
We can work around this for some datasources by using non-expiring credentials (e.g. basic auth). But for some datasources (e.g. Dataflow), OAuth2 is the only option.
We are considering creating our own service for updating credentials and triggering the refreshes, unless there is something available in the platform we are missing?
2 Replies
Aron_MooreSolution Specialist
We use a 'service' account that has credentials that don't expire.
mikelarahI'm not sure I understand? We also use 'service account' users to get around expiring passwords, but for the datasource credentials you have to provide an access token (not the username/password basic creds) which does expire.