|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Obsidian Git||3,713||a day ago||58||mit||TypeScript|
|Backup your Obsidian.md vault with git|
|Helm Secrets||974||14 days ago||1||apache-2.0||Shell|
|A helm plugin that help manage secrets with Git workflow and store them anywhere|
|Obsidian Vimrc Support||611||24 days ago||55||TypeScript|
|A plugin for the Obsidian.md note-taking software|
|Terraform Provisioner Ansible||526||2 years ago||22||December 06, 2020||10||apache-2.0||Go|
|Ansible with Terraform 0.14.x|
|Vault||407||10 months ago||3||lgpl-3.0||Java|
|Vault of common APIs for Bukkit Plugins|
|Vault Secrets Gen||317||3 months ago||17||August 11, 2022||2||mit||Go|
|A Vault secrets plugin for generating high entropy passwords and passphrases.|
|Awesome Vault Tools||256||a month ago||apache-2.0|
|Awesome tools around HashiCorp Vault|
|Hashicorp Vault Plugin||204||4 months ago||86||mit||Java|
|Jenkins plugin to populate environment variables from secrets stored in HashiCorp's Vault.|
|Vaultapi||200||a year ago||4||lgpl-3.0||Java|
|API Component of Vault|
|Vault Ethereum||200||a year ago||20||January 16, 2021||14||apache-2.0||Go|
|A plugin that turns Vault into an Ethereum wallet.|
This is a standalone backend plugin for use with Hashicorp Vault. This plugin provides Active Directory functionality to Vault.
Please note: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault, please responsibly disclose by contacting us at [email protected].
This is a Vault plugin and is meant to work with Vault. This guide assumes you have already installed Vault and have a basic understanding of how Vault works.
Otherwise, first read this guide on how to get started with Vault.
To learn specifically about how plugins work, see documentation on Vault plugins.
Please see documentation for the plugin on the Vault website.
This plugin is currently built into Vault and by default is accessed
ad. To enable this in a running Vault server:
$ vault secrets enable ad Success! Enabled the ad secrets engine at: ad/
Additionally starting with Vault 0.10 this backend is by default mounted
If you wish to work on this plugin, you'll first need Go installed on your machine (version 1.17+ is required).
For local dev first make sure Go is properly installed, including setting up a GOPATH.
To compile a development version of this plugin, run
This will put the plugin binary in the
mode will only generate the binary for your platform and is faster:
$ make $ make dev
Put the plugin binary into a location of your choice. This directory
will be specified as the
in the Vault config used to start the server.
plugin_directory = "path/to/plugin/directory"
Start a Vault server with this config file:
$ vault server -config=path/to/config.json ... ...
Once the server is started, register the plugin in the Vault server's plugin catalog:
$ vault plugin register \ -sha256=<SHA256 Hex value of the plugin binary> \ -command="vault-plugin-secrets-active-directory" \ secret \ custom-ad
Note you should generate a new sha256 checksum if you have made changes to the plugin. Example using openssl:
openssl dgst -sha256 $GOPATH/vault-plugin-secrets-ad ... SHA256(.../go/bin/vault-plugin-secrets-ad)= 896c13c0f5305daed381952a128322e02bc28a57d0c862a78cbc2ea66e8c6fa1
Enable the secrets plugin backend using the secrets enable plugin command:
$ vault secrets enable custom-ad ... Successfully enabled 'plugin' at 'custom-ad'!
If you are developing this plugin and want to verify it is still functioning (and you haven't broken anything else), we recommend running the tests.
To run the tests, run the following:
$ make test
You can also specify a
TESTARGS variable to filter tests like so:
$ make test TESTARGS='--run=TestConfig'