You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
Not sure when I last pushed or pulled from bitbucket, but I receiving "authentication not supported" when trying to push through https:// to my repo. The "account password" change effective March 1 according to what I've read = shouldn't impact (yet). I'm using Eclipse/egit - my cmd line skills are something to be desired.
I've replaced out some of the specifics with generics, but here is the Eclipse/java error flow:
Caused by: org.eclipse.jgit.errors.TransportException: https://user@bitbucket.org/user/foo.git: authentication not supported
at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:674)
at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:465)
at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:167)
... 5 more
I will play around in cmd line, but this def stops me in my tracks at the moment. Is this related to some of the other issues being reported a day or two ago w/ SSH comm doing what it looks - something similar if not the same?
Thank you.
FYI - I needed to change the SSL java from Apache to the built-in one; assuming whatever apache was running had on older version of TLS or something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.