Bitbucket Server "Token is not valid"

[sejalis]

Hi there!

I wanted to try out the new Bitbucket Server feature, but I'm already struggling with the login.

It seems like you are using the following request when logging in:
curl --location --request GET 'https://bitbucket.mycompanyname.country/rest/api/1.0/projects/' \ --header 'Authorization: Bearer PERS_TOKEN' \

which unfortunately fails for me in Fork:

although succeeds with postman:

We have a VPN connection within the company, might that be the issue for Fork?

Thanks in advance.
Cheers

[DanPristupov]

We have a VPN connection within the company, might that be the issue for Fork?

Not sure. Check if the log file ~/Library/Logs/Fork.log contains any error.

[sejalis]

looks like it:

[GitServiceConnection.swift:88] > 130ms: GET https://bitbucket.XXXXX.XXX/rest/api/1.0/application-properties (200)
BitbucketServerLoginController.swift:74] > unknown("Token is not valid")

Just wondering, how come that I'm getting this error?
According to the Documentation

there is no token needed, so I guess thats not the call which is failing?

Could you please share which endpoint you are using for the login? I'd like to try it locally via Postman

[DanPristupov]

@sejalis it's /rest/api/1.0/application-properties. Fork uses it to retrieve the X-AUSERNAME header.

[davidkaya]

I have the exact same issue. Could the logging be improved so we are able to troubleshoot it better?

[DanPristupov]

@davidkaya It's difficult because I don't have an access to such server.

Do you see the X-AUSERNAME header if you run:

curl "https://SERVERNAME/rest/api/1.0/application-properties" \ -H 'Authorization: Bearer <TOKEN>'?

[davidkaya]

Yep, I do:

...
< x-auserid: XXX
< x-ausername: XXX
...

[DanPristupov]

@davidkaya that's weird. Can you contact me by email, please? support@fork.dev

[sejalis]

sorry to get back so late to you. 😬
Seems like you resolved the issue (or IT updated the server or ... ? ), login has worked today. 👏