Summary
User facing login issues after migrating to abctl v0.11.1. API call to /api/login returns 200 with jwt and refresh token, but subsequent call to api/v1/users/get fails with 401 unauthorized. Issue seems to be related to authentication headers.
Question
Hi guys, still having login issues after migrating to abctl v0.11.1
https://airbytehq.slack.com/archives/C021JANJ6TY/p1722866695948209
Password is set through custom secret, user exists in user table, nothing suspicious in permission table. Upon further investigation it looks like the user and password are set up correctly, however:
when the correct username/password combination is entered, the api call to:
http://[my_airbyte_url]/api/login
• returns 200
• jwt and refresh token cookie is set
• new record is inserted into auth_refresh_token table
meanwhile the call to:
api/v1/users/get fails with 401 unauthorized
can’t see auth in headers
when I make a call with the generated token manually, for example:
body = {
"userId": "00000000-0000-0000-0000-000000000000"
}
headers = {
'Authorization': f'Bearer {token}'
}
url = f"{base_url}{'/v1/users/get'}"
res = requests.post(url=url, json=body, headers=headers)
return json.loads(res.content.decode('utf-8'))```
it runs just fine. Looks like it fails here in core js.
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1722892962949399) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["login-issues", "abctl-v0.11.1", "api", "authentication", "headers"]
</sub>