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

Random Port Assignments When Authenticating #39

Open
wagesj45 opened this issue Nov 29, 2018 · 3 comments
Open

Random Port Assignments When Authenticating #39

wagesj45 opened this issue Nov 29, 2018 · 3 comments

Comments

@wagesj45
Copy link

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?

@andresoviedo
Copy link
Owner

andresoviedo commented Nov 29, 2018

Good question. The port is managed by google api client library.

I will take a look to see if its possible to configure the port.

@andresoviedo
Copy link
Owner

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.

@vaibhavthapliyal
Copy link
Contributor

See pull request #45

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

3 participants