bwdc test returns a list of current user, so config seems fine per se:
root@vaultwarden:~# export BITWARDENCLI_CONNECTOR_PLAINTEXT_SECRETS=true
root@vaultwarden:~# export NODE_TLS_REJECT_UNAUTHORIZED=0
root@vaultwarden:~# bwdc test
{"groups":[],"enabledUsers":[{"externalId":"...","displayName":"user1@example.com"},...],"disabledUsers":[],"deletedUsers":[],"object":"test"}
bwdc sync however returns a semantic error:
root@vaultwarden:~# bwdc sync
(node:269114) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `bwdc --trace-warnings ...` to show where the warning was created)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="color-scheme" content="light dark">
<title>422 Unprocessable Entity</title>
</head>
<body align="center">
<div role="main" align="center">
<h1>422: Unprocessable Entity</h1>
<p>The request was well-formed but was unable to be followed due to semantic errors.</p>
<hr />
</div>
<div role="contentinfo" align="center">
<small>Rocket</small>
</div>
</body>
</html>
In the vaultwarden logs we get the following entries:
[2026-04-30 12:11:29.956][request][INFO] POST /api/public/organization/import
[2026-04-30 12:11:29.957][vaultwarden::api::core::public::_][WARN] Data guard `Json < OrgImportData >` failed: Parse("{\"groups\":[],\"members\":[{\"email\":\"user1@example.com\",\"externalId\":\"...\"},...],\"largeImport\":false}", Error("missing field `deleted`", line: 1, column: 112)).
[2026-04-30 12:11:29.957][response][INFO] (ldap_import) POST /api/public/organization/import => 422 Unprocessable Entity
Please try Version 2026.3.0 for now and see if that resolves the issue.
<!-- gh-comment-id:4352563985 -->
@BlackDex commented on GitHub (Apr 30, 2026):
Please try [Version 2026.3.0](https://github.com/bitwarden/directory-connector/releases/tag/v2026.3.0) for now and see if that resolves the issue.
Actually, it works just fine for me.
Could you provide the payload of the request please?
You should be able to extract that by going to View > Toggle Developer Tools > Network and then clear sync-cache and sync again. If that doesn't sync anything, you could also mark the Remove and re-add organization users during the next sync (For debugging purposes) at the bottom right.
<!-- gh-comment-id:4352648220 -->
@BlackDex commented on GitHub (Apr 30, 2026):
Actually, it works just fine for me.
Could you provide the payload of the request please?
You should be able to extract that by going to `View` > `Toggle Developer Tools` > `Network` and then clear sync-cache and sync again. If that doesn't sync anything, you could also mark the `Remove and re-add organization users during the next sync (For debugging purposes)` at the bottom right.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Kirodema on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7168
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.35.8
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
caddy v2.11.2
Host/Server Operating System
Linux
Operating System Version
No response
Clients
CLI
Client Version
bwdc 2026.04
Steps To Reproduce
1.) have a bwdc config to connect to a local ldap/AD server
~/.config/Bitwarden\ Directory\ Connector/data.json:
2.) run
bwdc syncExpected Result
bwdc should sync the ldap users as expected
Actual Result
bwdc testreturns a list of current user, so config seems fine per se:bwdc synchowever returns a semantic error:In the vaultwarden logs we get the following entries:
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Apr 30, 2026):
Please try Version 2026.3.0 for now and see if that resolves the issue.
@BlackDex commented on GitHub (Apr 30, 2026):
Actually, it works just fine for me.
Could you provide the payload of the request please?
You should be able to extract that by going to
View>Toggle Developer Tools>Networkand then clear sync-cache and sync again. If that doesn't sync anything, you could also mark theRemove and re-add organization users during the next sync (For debugging purposes)at the bottom right.