Closed KittyKatt closed 4 years ago
Is this on-prem or using Bitwarden cloud?
This is on-prem.
Maybe something is stale. Can you try logging out, check settings to make sure it is the right server URL, and then log in again.
I'll log out and try it again. It's worth noting I'm seeing that error message on the SERVER side, so I know it's hitting the right server. The server just thinks the organization (or the route to the API call) doesn't exist, so it's 404'ing there.
Yes, I was just wanting to see if the client had the wrong org id for some reason. Logging out and back in would refresh that.
I can confirm this issue. The server responses with a 404 error. Logout and login again doesn't change this behaviour. Calling the url directly in the browser gives the same error.
Is your user account an organization admin? If not that would return a 404 on this particular API.
Is your user account an organization admin? If not that would return a 404 on this particular API.
Of course, yes. My user is the only user in the system and I created the organization. ;)
Are you using the official Bitwarden server or some 3rd party community edition?
From your logs, looks like you are using bitwarden_rs. Please open an issue with them.
I've tried this in both the CLI and GUI versions of the application. I'm receiving a duplicate response as the one in issue #21. I didn't want to necro that issue, so here we are. My redacted configuration (from the CLI version) is as follows, with domain names, personal info, and infrastructure removed.
I get the error:
It's worth noting that even in the GUI, where the I select the Organization from the dropdown box, this is happening. When I run a test sync, the correct users come back so I know it's not an issue with the connection to the directory. It's definitely an issue with the OrganizationId being returned by BitWarden being...incorrect? Or something. I can load that organization in the web UI and the same string that's returned in the error message is in the URL, so it seems at a glance to be correct. Not sure what's going on here.