{"action":"opened","issue":{"url":"https://api.github.com/repos/hashicorp/vault/issues/1565","repository_url":"https://api.github.com/repos/hashicorp/vault","labels_url":"https://api.github.com/repos/hashicorp/vault/issues/1565/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/vault/issues/1565/comments","events_url":"https://api.github.com/repos/hashicorp/vault/issues/1565/events","html_url":"https://github.com/hashicorp/vault/issues/1565","id":162548550,"number":1565,"title":"root ability to lookup a token ID by display name or accessor","user":{"login":"gandg","id":161420,"avatar_url":"https://avatars.githubusercontent.com/u/161420?v=3","gravatar_id":"","url":"https://api.github.com/users/gandg","html_url":"https://github.com/gandg","followers_url":"https://api.github.com/users/gandg/followers","following_url":"https://api.github.com/users/gandg/following{/other_user}","gists_url":"https://api.github.com/users/gandg/gists{/gist_id}","starred_url":"https://api.github.com/users/gandg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gandg/subscriptions","organizations_url":"https://api.github.com/users/gandg/orgs","repos_url":"https://api.github.com/users/gandg/repos","events_url":"https://api.github.com/users/gandg/events{/privacy}","received_events_url":"https://api.github.com/users/gandg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-27T21:07:33Z","updated_at":"2016-06-27T21:07:33Z","closed_at":null,"body":"Perhaps this is on the list already, but the use case I have is.  A vault admin creates a new token based on a policy.  The token ID is revealed as part of the create and must be saved \"somewhere\" so as to later give the ID to a sys admin to place in a java keystore such that an App can start up, read the token ID and then use it to read its needed secrets from the vault.  Would be great if the vault admin could create tokens in one step, then later look them up (token-lookup is a big help) and actually see the original token ID.  Without this capability, the vault admin needs to manually store the token ID in a cubbyhole for later use - effectively storing it twice.  My thought is to allow the root user to lookup and see the original tokenID info altogether as part of the token-lookup output.  Maybe this could be implemented with a special -root flag.  I could be missing something here, or maybe this is being considered down the road.  "}}
{"actor":{"display_login":"gandg"}}