Bug 1041840

Summary: [RFE][python-keystoneclient]: --os-token is unweildy for use with PKI tokens
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/python-keystoneclient/+spec/specify-clientside-token-file
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:54:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 19:39:17 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/python-keystoneclient/+spec/specify-clientside-token-file.

Description:

Commonly used UUID tokens are of a reasonably length to be specified as CLI arguments. However, given the potential length of base64-encoded PKI tokens, this approach becomes unwieldy.

This blueprint would introduce two new options complement the existing OS_TOKEN environment variable and --os-token CLI argument:

    OS_TOKEN_FILE=/abs/path/to/token

    --os-token-file=/abs/path/to/token

If --os-token-file is provided along with OS_TOKEN_FILE, --os-token-file should take precedence.
If either --os-token or OS_TOKEN is provided along with either OS_TOKEN_FILE or  --os-token-file, an error should be raised.

Specification URL (additional information):

None