We ran into this scenario when running some tests using two different identities. The test was done on a vagrant VM where we had two terminal windows open. Let's refer to them as terminal1 and terminal2
On terminal1, login to CloudFoundry as user: foo@mycompany.com
$ cf login --username foo@mycompany.com --password XXXXXXXX -o fooOrg -s development
target: https://api.cf.att.io
Authenticating... OK
Switching to organization fooOrg... OK
Switching to space development... OK
On terminal 1, check the space for user foo@mycompany.com
$ cf space
development:
organization: fooOrg
apps: none
services: none
domains: cf.att.io
On terminal2, login to Cloud Foundry as a different user: bar@mycompany.com
$ cf login --username bar@mycompany.com --password YYYYYYYY -o barOrg -s development
target: https://api.cf.att.io
Authenticating... OK
Switching to organization barOrg... OK
Switching to space development... OK
Back on terminal1, let's check the space again for user foo@mycompany.com now
$ cf space
development:
organization: barOrg
apps: hello-redis-node1, hello-redis-node, caldecott
services: redis-1bc1, redis-test, svc-test1
domains: cf.att.io
There was no message or warning displayed to the user on any of the terminal windows that the organization/space was changing.
We ran into this scenario when running some tests using two different identities. The test was done on a vagrant VM where we had two terminal windows open. Let's refer to them as terminal1 and terminal2
On terminal1, login to CloudFoundry as user: foo@mycompany.com
$ cf login --username foo@mycompany.com --password XXXXXXXX -o fooOrg -s development
target: https://api.cf.att.io
Authenticating... OK
Switching to organization fooOrg... OK
Switching to space development... OK
On terminal 1, check the space for user foo@mycompany.com
$ cf space
development:
organization: fooOrg
apps: none
services: none
domains: cf.att.io
On terminal2, login to Cloud Foundry as a different user: bar@mycompany.com
$ cf login --username bar@mycompany.com --password YYYYYYYY -o barOrg -s development
target: https://api.cf.att.io
Authenticating... OK
Switching to organization barOrg... OK
Switching to space development... OK
Back on terminal1, let's check the space again for user foo@mycompany.com now
$ cf space
development:
organization: barOrg
apps: hello-redis-node1, hello-redis-node, caldecott
services: redis-1bc1, redis-test, svc-test1
domains: cf.att.io
There was no message or warning displayed to the user on any of the terminal windows that the organization/space was changing.