You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The authentication step that produces the link to follow in a browser to authenticate gdfa uses a callback URI. The port that it listens to seems to be random each time the service is started. Could that be standardized, or is there a way to predict what port it will listen to?
The text was updated successfully, but these errors were encountered:
Not sure about the motivation of having a dedicated localhost port. What is your use case?
In case that's feasible, I suppose we would need to create a new property and configure Google drive API client with specified port
If anyone wants to push a merge request, please make sure it works with and without specifying port in configuration.
Only commit the ¿ 2 ? files that may me be impacted.
The authentication step that produces the link to follow in a browser to authenticate gdfa uses a callback URI. The port that it listens to seems to be random each time the service is started. Could that be standardized, or is there a way to predict what port it will listen to?
The text was updated successfully, but these errors were encountered: