Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Open the aeolus-conductor and provide user credential of some user say User1. 2.Open the aeolus-conductor and provide user credential of some user say User2. Actual results: Now browser session that opened with user1 changed and start navigating using credential of user2. Expected results: Both browser session should keep only their own user information.(same as Amazon ec2 console) Additional info:
build info:- [root@dell-pe1950-1 ~]# rpm -qa |grep aeolus aeolus-conductor-0.8.3-1.el6.noarch aeolus-conductor-daemons-0.8.3-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-all-0.8.3-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.3-1.el6.noarch
You say "different browser session" -- are you really using different browsers or just different windows/tabs of the same browser? If the latter, the two windows share the same cookies, so it's the same login -- any web UI that uses cookies for session-tracking (rather than URLs) will show the same behavior. For active testing of two users at once you should run two completely different browsers -- say firefox and chrome -- so you can have two different users logged in concurrently (but in different sessions)
(In reply to comment #2) > You say "different browser session" -- are you really using different browsers > or just different windows/tabs of the same browser? If the latter, the two > windows share the same cookies, so it's the same login -- any web UI that uses > cookies for session-tracking (rather than URLs) will show the same behavior. > > For active testing of two users at once you should run two completely different > browsers -- say firefox and chrome -- so you can have two different users > logged in concurrently (but in different sessions) Agreed.. Pushpesh the requirement would be to use two or three diff browsers. Chrome, firefox, Opera Thanks