open-vault/builtin/credential/approle
Jeff Mitchell 6bf871995b Don't use time.Time in responses. (#1912)
This fixes #1911 but not directly; it doesn't address the cause of the
panic. However, it turns out that this is the correct fix anyways,
because it ensures that the value being logged is RFC3339 format, which
is what the time turns into in JSON but not the normal time string
value, so what we audit log (and HMAC) matches what we are returning.
2016-09-23 12:32:07 -04:00
..
backend.go Safely manipulate secret id accessors 2016-09-15 18:13:50 -04:00
backend_test.go AppRole authentication backend 2016-07-26 09:32:41 -04:00
path_login.go AppRole authentication backend 2016-07-26 09:32:41 -04:00
path_login_test.go AppRole authentication backend 2016-07-26 09:32:41 -04:00
path_role.go Don't use time.Time in responses. (#1912) 2016-09-23 12:32:07 -04:00
path_role_test.go Ensure at least one constraint on the role 2016-09-13 16:03:15 -04:00
path_tidy_user_id.go Convert to logxi 2016-08-21 18:13:37 -04:00
validation.go Safely manipulate secret id accessors 2016-09-15 18:13:50 -04:00