Trying to authenticate opens localhost on port 9090 and not jira/bitbucket (V1.2.3)

[Alon Menczer]

When i try to authenticate, a tab opens in my browser but it leads to localhost:9090 for some reason (which is a local service i use)
How can i configure what URL should it use?

[Ciro Nunes]

Same here

[Rishabh Mishra]

same

[Joachim Van den Abeele]

I had the same problem. I was able to solve it by opening the developer tools of visual studio code (execute command “Developer: Toggle developer tools”) which made it clear I was already running something on port 9090. If you make sure nothing is running on that port you will be able to authenticate.

[Alon Menczer]

I had port forwarding for this port - removing it worked.
It seems like this is only needed for the first login.
Anyway, that’s a weird prerequisite,
I think this should be solved.

[Jonathan Doklovic]

The extension needs to listen on 127.0.0.1:9090 to complete the OAuth flow when you authenticate. After authentication, the listener is no longer needed and is shutdown automatically.

This means that port 9090 needs to be free when authenticating with the extension.

Unfortunately, both Jira dn Bitbucket require us to fill in the redirect URL at the time the OAuth consumer is created and it’s currently not possible to override at authentication time. This means we cannot use a dynamically picked port at this time.

[Patrick Fowler]

9090 is a default port for a lot of node api projects. If you’re developing node, there’s a pretty good chance you have your server running on 9090, and this extension is dead on arrival. Really a shame to see something like this released to the public

[Jason Henriksen]

I confirmed that I have NOTHING running on 127.0.0.1:9090 I still have the same problem.

However, I do see a stack trace that says:
stack trace: Error: self signed certificate in certificate chain

I know why that cert is there and I need it to be there. But maybe that is causing the problem?

I’d love to use this extension, but it’s not possible until this is fixed.

[Pramod Busam]

We changed the port from 9090 to 31415 in version 1.3.0 of the extension. Please update and let us know if it fixes the login flow.