Description of problem:
After adding a server which is using mutual SSL authentication and x509 certificates, when switch back to this server using 'rhc server use <hostname>', rhc client always prompt user to generate a token.

Version-Release number of selected component (if applicable):
rhc-1.28.5.1-1.el6op.noarch

How reproducible:
always

Steps to Reproduce:
1.Add the server using 'rhc server add '
[root@dhcp-129-188 ~]# rhc server add broker.ose21z-0808.x509.com ose1 --ssl-ca-file File --ssl-client-cert-file File --ssl-client-key-file File

OpenShift can create and store a token on disk which allows to you to access the server without using your password. The key is stored in your
home directory and should be kept secret.  You can delete the key at any time by running 'rhc logout'.
Generate a token now? (yes|no) yes
Generating an authorization token for this client ... lasts about 6 hours

Saving server configuration to /root/.openshift/servers.yml ... done


2.Check the generated token
[root@dhcp-129-188 ~]# ls ~/.openshift/token_*
/root/.openshift/token_ZeeQxFyYeexGoLjbqgHKQ
[root@dhcp-129-188 ~]# cat /root/.openshift/token_ZeeQxFyYeexGoLjbqgHKQ
e8d565c16827100d32e9e832e8c6a60de5b7079e29b801259071a741b1208fb8


3.Switch to this server
[root@dhcp-129-188 ~]# rhc server use ose1
Using gpei to login to broker.ose21z-0808.x509.com

OpenShift can create and store a token on disk which allows to you to access the server without using your password. The key is stored in your
home directory and should be kept secret.  You can delete the key at any time by running 'rhc logout'.
Generate a token now? (yes|no) yes
Generating an authorization token for this client ... lasts about 5 hours

Saving configuration to /root/.openshift/express.conf ... done
Saving server configuration to /root/.openshift/servers.yml ... done

Now using 'broker.ose21z-0808.x509.com'


4. Check existing token again. Still the same token.
[root@dhcp-129-188 ~]# ls ~/.openshift/token_*
/root/.openshift/token_ZeeQxFyYeexGoLjbqgHKQ
[root@dhcp-129-188 ~]# cat /root/.openshift/token_ZeeQxFyYeexGoLjbqgHKQ
e8d565c16827100d32e9e832e8c6a60de5b7079e29b801259071a741b1208fb8


Actual results:

Expected results:
Should using the existing token.

Additional info:
This wouldn't happen on a normal ose broker.
[root@dhcp-129-188 ~]# rhc server use ose2
Using an existing token for gpei to login to xxx.xxx.xx.xx

Saving configuration to /root/.openshift/express.conf ... done
Saving server configuration to /root/.openshift/servers.yml ... done

Now using 'xxx.xxx.xx.xx'