mirror of
https://github.com/hashicorp/vault.git
synced 2026-01-23 09:31:55 +01:00
revert more unnecessary dep changes
This commit is contained in:
parent
6bbba884b1
commit
d65ebddf89
2
go.mod
2
go.mod
@ -75,7 +75,7 @@ require (
|
||||
github.com/hashicorp/vault-plugin-auth-jwt v0.5.1
|
||||
github.com/hashicorp/vault-plugin-auth-kubernetes v0.5.1
|
||||
github.com/hashicorp/vault-plugin-auth-pcf v0.0.0-20190619165123-fb996be2877c
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190617182336-fe4c97e18808
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190508211750-4152192cdc0f
|
||||
github.com/hashicorp/vault-plugin-secrets-ad v0.5.1
|
||||
github.com/hashicorp/vault-plugin-secrets-alicloud v0.5.1
|
||||
github.com/hashicorp/vault-plugin-secrets-azure v0.5.1
|
||||
|
||||
2
go.sum
2
go.sum
@ -295,6 +295,8 @@ github.com/hashicorp/vault-plugin-auth-pcf v0.0.0-20190605234735-619218abcd26 h1
|
||||
github.com/hashicorp/vault-plugin-auth-pcf v0.0.0-20190605234735-619218abcd26/go.mod h1:9866PkjxPBXclbEJBKzVGY60pgVIY9b7qZJ5Fa+p6VY=
|
||||
github.com/hashicorp/vault-plugin-auth-pcf v0.0.0-20190619165123-fb996be2877c h1:/g4Yr7pCTfKVqjUUVO4/Pkd3Vmw2TB3znuB4lF7ZNNY=
|
||||
github.com/hashicorp/vault-plugin-auth-pcf v0.0.0-20190619165123-fb996be2877c/go.mod h1:AjWJZO3nIHzc1inkx57x5qtIIcpi1sejXiwJVcNpjyc=
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190508211750-4152192cdc0f h1:BYQVawXauMXQ26I3Pn1Nw9kp/aZD60xmh9ZP3jum0YM=
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190508211750-4152192cdc0f/go.mod h1:CkOYWfeuC5nAzehBztl94S6VOn2g50h1tffpcNoWCZ8=
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190617182336-fe4c97e18808 h1:taTbXUW9En/vHp7tVdjhO5XLUmHYxuFJZar+35H7PPg=
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190617182336-fe4c97e18808/go.mod h1:CkOYWfeuC5nAzehBztl94S6VOn2g50h1tffpcNoWCZ8=
|
||||
github.com/hashicorp/vault-plugin-secrets-ad v0.5.1 h1:BdiASUZLOvOUs317EnaUNjGxTSw0PYGQA7zJZhDKLC4=
|
||||
|
||||
25
vendor/github.com/hashicorp/vault-plugin-database-elasticsearch/README.md
generated
vendored
25
vendor/github.com/hashicorp/vault-plugin-database-elasticsearch/README.md
generated
vendored
@ -4,19 +4,23 @@ This plugin provides unique, short-lived credentials for Elasticsearch using nat
|
||||
## Getting Started
|
||||
|
||||
To take advantage of this plugin, you must first enable Elasticsearch's native realm of security by activating X-Pack. These
|
||||
instructions will walk you through doing this using ElasticSearch 7.1.1.
|
||||
instructions will walk you through doing this using ElasticSearch 6.6.1. At the time of writing, X-Pack was a paid feature.
|
||||
To use it, you may need to enable a 30-day trial with Elasticsearch, or activate a paid version.
|
||||
|
||||
### Enable X-Pack Security in Elasticsearch
|
||||
|
||||
Read [Securing the Elastic Stack](https://www.elastic.co/guide/en/elastic-stack-overview/7.1/elasticsearch-security.html) and
|
||||
follow [its instructions for enabling X-Pack Security](https://www.elastic.co/guide/en/elasticsearch/reference/7.1/setup-xpack.html).
|
||||
Read [Securing the Elastic Stack](https://www.elastic.co/guide/en/elastic-stack-overview/6.6/elasticsearch-security.html) and
|
||||
follow [its instructions for enabling X-Pack Security](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/setup-xpack.html).
|
||||
When done, verify that you've enabled X-Pack by running `$ $ES_HOME/bin/elasticsearch-setup-passwords interactive`. You'll
|
||||
know it's been set up successfully if it takes you through a number of password-inputting steps.
|
||||
|
||||
### Enable Encrypted Communications
|
||||
### Recommended: Enable Encrypted Communications
|
||||
|
||||
This plugin communicates with Elasticsearch's security API. In ES 7.1.1, you must enable TLS to consume that API.
|
||||
This plugin communicates with Elasticsearch's security API. We recommend you enable TLS for these communications so they can be
|
||||
encrypted.
|
||||
|
||||
To set up TLS in Elasticsearch, first read [encrypted communications](https://www.elastic.co/guide/en/elastic-stack-overview/7.1/encrypting-communications.html)
|
||||
and go through its instructions on [encrypting HTTP client communications](https://www.elastic.co/guide/en/elasticsearch/reference/7.1/configuring-tls.html#tls-http).
|
||||
To set up TLS in Elasticsearch, first read [encrypted communications](https://www.elastic.co/guide/en/elastic-stack-overview/6.6/encrypting-communications.html)
|
||||
and go through its instructions on [encrypting HTTP client communications](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/configuring-tls.html#tls-http).
|
||||
|
||||
After enabling TLS on the Elasticsearch side, you'll need to convert the .p12 certificates you generated to other formats so they can be
|
||||
used by Vault. [Here is an example using OpenSSL](https://stackoverflow.com/questions/15144046/converting-pkcs12-certificate-into-pem-using-openssl)
|
||||
@ -30,11 +34,6 @@ and using `sudo dpkg-reconfigure ca-certificates`.
|
||||
The above instructions may vary if you are not using an Ubuntu machine. Please ensure you're using the methods specific to your operating
|
||||
environment. Describing every operating environment is outside the scope of these instructions.
|
||||
|
||||
### Set Up Passwords
|
||||
|
||||
When done, verify that you've enabled X-Pack by running `$ $ES_HOME/bin/elasticsearch-setup-passwords interactive`. You'll
|
||||
know it's been set up successfully if it takes you through a number of password-inputting steps.
|
||||
|
||||
### Create a Role for Vault
|
||||
|
||||
Next, in Elasticsearch, we recommend that you create a user just for Vault to use in managing secrets.
|
||||
@ -82,7 +81,7 @@ Here is an example of how to successfully configure and use this secrets engine
|
||||
`plugin_name` may need to be `vault-plugin-database-elasticsearch` if you manually mounted it rather than using the
|
||||
version of the plugin built in to Vault.
|
||||
```
|
||||
export ES_HOME=/home/somewhere/Applications/elasticsearch-7.1.1
|
||||
export ES_HOME=/home/somewhere/Applications/elasticsearch-6.6.1
|
||||
|
||||
vault secrets enable database
|
||||
|
||||
|
||||
2
vendor/modules.txt
vendored
2
vendor/modules.txt
vendored
@ -342,7 +342,7 @@ github.com/hashicorp/vault-plugin-auth-pcf/models
|
||||
github.com/hashicorp/vault-plugin-auth-pcf/util
|
||||
github.com/hashicorp/vault-plugin-auth-pcf/testing/certificates
|
||||
github.com/hashicorp/vault-plugin-auth-pcf/testing/pcf
|
||||
# github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190617182336-fe4c97e18808
|
||||
# github.com/hashicorp/vault-plugin-database-elasticsearch v0.0.0-20190508211750-4152192cdc0f
|
||||
github.com/hashicorp/vault-plugin-database-elasticsearch
|
||||
# github.com/hashicorp/vault-plugin-secrets-ad v0.5.1
|
||||
github.com/hashicorp/vault-plugin-secrets-ad/plugin
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user