When we moved a current Vault (2.1.2) to OpenBao 2.7.1 in our lab, 17 of its 26 plugin mounts stopped serving. They stayed in the mount list, the API answered backend is nil, and the only other sign was an ERROR line in the server log.
Most of those mounts don't have to stay dead. OpenBao keeps a separate repository, openbao-plugins, with plugins that aren't in the main binary. We checked our list of 17 against it.
What has a plugin, and what doesn't
| Vault mount | Kind | OpenBao plugin |
|---|---|---|
| AWS, Azure, GCP | secrets engine | yes |
| Consul, Nomad, LDAP | secrets engine | yes |
| AWS, Azure, GCP, GitHub | auth method | yes |
| Kerberos, LDAP, RADIUS | auth method | yes |
agent-registry/ | secrets engine | no |
| AliCloud, Cloud Foundry, Okta | auth method | no |
That makes 13 with a plugin and 4 without. Twelve of the 13 had a release on 26 October 2026, the day OpenBao 2.7.2 shipped its security fixes. Kerberos had its first on 2 October, and the AWS secrets engine had another on 4 November. These are maintained, not abandoned forks.
The four without a plugin need a decision before the swap.
agent-registry/is created by default on every Vault 2.x install. If nothing uses it, disable it in Vault first and the error goes away.- Okta, AliCloud and Cloud Foundry auth have no OpenBao counterpart. Anyone who signs in through one of them needs another route first. OIDC and JWT auth are built in, and both kept serving in our lab, so an identity provider that speaks OIDC, Okta included, is the usual way across.
Declare the plugins before the first OpenBao node starts
OpenBao's migration guide assumes no external plugins. If you use any of the 13, the plugins repository says to declare each one in the server config, with plugin_directory set and plugin_auto_download = true, then enable it. A declared plugin is pinned to an image tag and digest, so you know exactly what runs.
Do it in the config you bring up on the first OpenBao node, not after. A follower-first rolling upgrade puts OpenBao in charge of serving before you've finished, and a mount whose plugin isn't declared serves nothing from that moment.
What we haven't tested yet
We have not run the migration with these plugins declared. So we can't yet tell you whether a migrated mount picks up its stored configuration from a declared plugin, or whether it needs re-creating and re-configuring. That's the next run in our lab, and we'll write it up. Until then, treat it as unknown and keep a copy of each mount's configuration outside Vault before you start.
Before you move
- Run
vault secrets listandvault auth list, and check each type against the table above. - For each mount with no plugin, decide what replaces it, and move its users first.
- Declare every plugin you need in the OpenBao config, pinned by digest.
- Take a raft snapshot. In our lab it was the only rollback that worked.
Planning a move off Vault and want it rehearsed against your own mounts first? Talk to us.