<@U07G9BFC3HT> you can try different endpoint https://reference.airbyte.com/reference/listuserswithinanorganization
for abctl installation it might contain /api/public prefix depending on Airbyte’s version: /api/public/v1/users
https://reference.airbyte.com/reference/standalone-server-deprecation-and-migration-to-airbyte-server
Thank you for the response. I pivoted to installing airbyte on our k8s cluster and used the tailscale ingress controller rather than using the docker desktop deployment method.
We are still looking into why the username doesn’t always pre-populate. In the meanwhile our “official” workaround to how to get it manually is documented https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#unable-to-locate-user-email|here. Sorry for the inconvenience!
<@U02U116B8BB> I think it is not only me, In my case my problem is not perfectly solved. It does two calls
- http://myinternal.url.cloud:8000/api/login success It gets token and refresh
- http://myinternal.url.cloud:8000/api/v1/users/get fails 401 unauthorized
There a few hacky way to solve this issue like tunnelling but it is not good enough to share it even for internal PoC demo, (ie it works only on my computer)