Bug 1011326 - [origin_broker_113] The value of 'secret_token' in mongo did not change after reset 'OPENSHIFT_SECRET_TOKEN'
Summary: [origin_broker_113] The value of 'secret_token' in mongo did not change after...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 05:43 UTC by zhaozhanqi
Modified: 2015-05-15 00:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-17 13:30:51 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description zhaozhanqi 2013-09-24 05:43:08 UTC
Description of problem:
create one app and reset the env variable 'OPENSHIFT_SECRET_TOKEN', after do that, the OPENSHIFT_SECRET_TOKEN has been changed, but in mongo the value 'secret_token' did not change.

Version-Release number of selected component (if applicable):
devenv_3816

How reproducible:
always

Steps to Reproduce:
1. create one any type app
2. reset the value of env variable OPENSHIFT_SECRET_TOKEN
    rhc env set OPENSHIFT_SECRET_TOKEN=hello -a $app
3. rhc ssh -a $app --gear env |grep -i variable OPENSHIFT_SECRET_TOKEN
4. check mongo db

Actual results:

step 3: OPENSHIFT_SECRET_TOKEN=hello
step 4: the value of secret_token did not change
"secret_token" "g1F41sFyHjLOZnM8_122BnkpL1Wds4RaRw2zv4Lidv1tcvtUr3VHrrh5Ym9SDxXFxxsEbSOK3R2XjUv4B8MdPZsIVXdfUOz6zHqCJGBsOmhm_jYJ_Hz-pxkLYyYXzJa-"

Expected results:
the value of 'secret_token' in mongo should be also changed and keep consistent with OPENSHIFT_SECRET_TOKEN

Additional info:

Comment 1 Abhishek Gupta 2013-09-24 22:49:51 UTC
This is as expected. The user can set/reset the environment variable and the token stored in mongo will not be updated. The secret token stored in mongo is the system generated token and can be overridden by the user. The user specified environment variable will take effect in such cases. If the user decides to unset/remove the environment variable, then the system generated secret token will once again be applicable.

Comment 2 zhaozhanqi 2013-09-25 01:56:34 UTC
according to comment 1, it is by design, so close this bug.


Note You need to log in before you can comment on or make changes to this bug.