Commit Graph

144 Commits

Author SHA1 Message Date
Marien Fressinaud
c248375372 [doc] Change auth token in getting-started (#4118)
In the authentication section of the getting started doc, the token used
to login doesn't match with the one displayed as the command result.

This commit makes sure that both tokens correspond to avoid distracting
newcomers.
2018-03-13 10:28:09 -04:00
Jed
b020d310e4 Lil typo fixes (#3925)
Read through the initial docs and noticed a few typos
2018-02-07 09:38:11 -05:00
George Christou
feb47cbf7f website: Include fish as a supported shell (#3895) 2018-02-02 10:34:48 -05:00
Harrison Brown
7b7537d936 Suggested website copy changes (#3791)
* Adds comma

* Adds comma

* Suggested copy change
2018-01-15 14:33:41 -05:00
Seth Vargo
50caac0bb6
More naming cleanup 2017-10-24 09:35:03 -04:00
Seth Vargo
ec79e1ddde
Update getting started walkthrough 2017-10-24 09:34:30 -04:00
Seth Vargo
23d1d9a1ac
Resolve the most painful merge conflict known on earth 2017-10-24 09:34:12 -04:00
Seth Vargo
b8e4b0d515
Standardize on "auth method"
This removes all references I could find to:

- credential provider
- authentication backend
- authentication provider
- auth provider
- auth backend

in favor of the unified:

- auth method
2017-10-24 09:32:15 -04:00
Chris Hoffman
010575cb60 Rename "generic" secret backend to "kv" (#3292) 2017-09-15 09:02:29 -04:00
Dan Urson
e22d7074b4 Update AWS CloudHSM comparison. (#3311)
* Update AWS CloudHSM comparison.

* Update hsm.html.md

* Update hsm.html.md
2017-09-10 12:54:05 -04:00
Chris Maki
f36f0066a5 Update policies.html.md
Using the latest vault release, I was getting the following error when the policy used `write`:

Error: Error making API request.

URL: PUT http://0.0.0.0:8200/v1/sys/policy/secret
Code: 400. Errors:

* Failed to parse policy: path "secret/*": invalid capability 'write'

I think `create` is the correct new Capability.
2017-08-17 12:26:29 -07:00
Brian Kassouf
1d03ad7420 Fix a few links (#3188) 2017-08-16 10:27:12 -07:00
Jonathan Duncan
0879694c3c Updated policy format to use capabilities keyword (#3063)
The `policy` key name is deprecated and has been replaced with `capabilities`.
2017-07-26 14:05:11 -04:00
Seth Vargo
31e8349197 Update Policies and Auth concepts pages (#3011) 2017-07-14 11:15:22 -04:00
Jeff Mitchell
d0d3b7c0ec More cleanup
Ping #2894
2017-06-20 10:46:24 -04:00
Ken McVicker
1da5e2b135 Update install.html.md
Updates list of commands with the output of 0.6.4.  Missing commands list, unwrap, capabilities, generate-root
2017-05-12 14:13:06 -06:00
Seth Vargo
a8591fbd81
Links 2017-03-17 14:27:32 -04:00
Seth Vargo
f64bf8d183
/docs/http -> /api 2017-03-17 14:06:03 -04:00
Michael
3445b3ae63 Updated doc to match real output (#2443)
Regards hashicorp/vault#2116
2017-03-06 10:39:34 -05:00
Frank Gevaerts
6d49eb7b8f Update hsm.html.md (#2381) 2017-02-16 07:25:22 -05:00
Jack Harris
6f4da5ff07 Add correct output to unmount documentation (#2352)
Simply adding the actual output of: 'vault unmount generic/'
2017-02-08 10:40:56 -05:00
windowsrefund
b77ad87bd5 prevent startup error when user has multiple private IPs configured locally 2017-01-03 15:24:11 -05:00
Jeff Mitchell
0d92169aef Update vs HSM text 2016-12-28 11:23:50 -05:00
James Turnbull
f595e40b8e Edits to the deploy guide 2016-12-14 11:17:50 -05:00
James Turnbull
95ef6552de Edits to the authorization/acl guide 2016-12-14 11:11:14 -05:00
James Turnbull
7248d6ace5 Edits to the authentication guide 2016-12-14 11:06:42 -05:00
James Turnbull
a2352aa13e Formatting and language updates to help guide 2016-12-14 10:55:11 -05:00
James Turnbull
84ab440473 Minor formatting fix to dynamic secrets guide 2016-12-14 10:51:56 -05:00
James Turnbull
ae22f93636 Updated some formatting and language in the secret backends doc 2016-12-14 10:46:14 -05:00
James Turnbull
8f6ad20db1 Updated some formatting and language in the first secret doc 2016-12-14 10:39:45 -05:00
James Turnbull
cbb44b4eed Updated some language and formatting in the dev-server guide 2016-12-14 10:34:52 -05:00
James Turnbull
3122856663 Edits to the install doc in getting started 2016-12-14 10:15:26 -05:00
James Turnbull
f9bde3edfb Added next step to install section 2016-12-14 10:13:15 -05:00
Andrea Crotti
5b9c125954 return code is 403 not 400 (#2128) 2016-11-25 06:47:27 -08:00
Em Smith
fba6068e97 Change command examples for First Secrets #2116 (#2117)
These were discovered to be out of date as per https://github.com/hashicorp/vault/issues/2116
2016-11-22 12:44:17 -05:00
vishalnayak
52419be7c9 s/localhost/127.0.0.1 2016-10-28 09:23:05 -04:00
vishalnayak
81410d7bc4 Using AppRole as an example. Removed 'root' policy being used in examples 2016-10-28 01:24:25 -04:00
vishalnayak
956fa432be Update the getting started API doc to not use 'root' policy 2016-10-11 16:07:48 -04:00
Jeff Mitchell
c748ff322f Change default TTL from 30 to 32 to accommodate monthly operations (#1942) 2016-09-28 18:32:49 -04:00
Jeff Mitchell
9e68c5ebf6 Update getting started docs since root can no longer be used from github 2016-09-26 13:09:26 -04:00
John
380bbfca36 tip to override VAULT_ADDR in getting started guide (#1915) 2016-09-23 19:34:07 -04:00
Michael Warkentin
2a5c883ca4 Out of date code
Looks like the `500` is now a `405`:

```
$ vault read aws/config/root
Error reading aws/config/root: Error making API request.

URL: GET http://127.0.0.1:8200/v1/aws/config/root
Code: 405. Errors:

* 1 error(s) occurred:

* unsupported operation
```
2016-09-12 15:58:25 -04:00
khanklatt
1b9ee9fed4 Correcting typo on "mechanisms" (#1822) 2016-09-01 09:53:20 -04:00
Jeff Mitchell
ef14e1b88f Bump version 2016-08-22 09:19:13 -04:00
Jeff Mitchell
0dad4c807b Remove old terraform page 2016-08-08 08:26:05 -04:00
Brian Shumate
877a7dc378 Minor grammar edit 2016-07-06 10:02:52 -04:00
Brian Shumate
7f5212307e Update deploy.html.md
Corrected link to Using PGP, GPG, and Keybase
2016-06-21 12:14:58 -04:00
Jeff Mitchell
4d5686452b Merge pull request #1324 from hashicorp/sethvargo/doc_gpg
Add a page for step-by-step gpg/keybase
2016-06-03 13:24:57 -04:00
Jeff Mitchell
bcf7f3ddb9 Make some updates to PGP documentation 2016-06-03 13:23:20 -04:00
Sami Rageb
0a8a7cba24 Fixed & clarified grammar around HCL & JSON
- Fixed the statement that HCL is JSON compatible, it's vice versa
- Added that HCL is a superset of JSON to eliminate any lingering confusion
2016-05-26 20:14:59 -05:00