New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessor paths for lookup and revocation of tokens #1188
Conversation
…or code in all the responses
@@ -28,6 +28,7 @@ type Secret struct { | |||
// SecretAuth is the structure containing auth information if we have it. | |||
type SecretAuth struct { | |||
ClientToken string `json:"client_token"` | |||
AccessorID string `json:"accessor_id"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is going to be an annoying code change, but...I don't like "AccessorID". I used "Accessor" in the RFC because it's a noun; calling it an AccessorID means that it's an ID of the accessor, which is not what it is. "AccessID" could work, but I preferred Accessor over AccessID because AccessID could be confused as the actual important value (a value to "access Vault").
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an annoying change :) I'll do it.
Looking pretty good, left a few comments. |
6e0e5fd
to
c7c9e0b
Compare
LGTM! |
Accessor paths for lookup and revocation of tokens
API documentation and Tests pending. Do Not Merge.