New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 676242 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Save PWD for the user is not updated correctly

Reported by dilraj...@gmail.com, Dec 21 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Create two users with same name in difference instance urls
2. Create seperate pwds for the users

3. While login chrome prompts user to save pwd

4. Now open the second instance url and chrome autofills the user and pwd which was saved from first instance

5. Login with the second pwd, then chrome prompts to update pwd

What is the expected behavior?
Chrome should remember the User and Pwd along with the URL accessed. 

What went wrong?
At present it is saving pwd for the user only. I can have same user id in different instance with different pwd. The same working fine in Firefox.

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

Comment 1 by brajkumar@chromium.org, Jan 13 2017

Cc: brajkumar@chromium.org
Components: -UI UI>Browser>Autofill
Labels: Needs-Feedback
Tested this issue on Windows-10 using chrome latest stable M55-55.0.2883.87 by following steps mentioned below.

1. Created an account for facebook.com & twitter.com using similar username and different password
2. Entered username and password manually for facebook and clicked on login, Observed the save prompt displayed to save the credetials
3. Clicked on save
4. Navigated to twitter.com and observed the usernam is already available in the username field left password blank
5. Provided different password manually and clicked on login, Observed the save prompt displayed to save the credetials
6. Clicked on save
7. Closed chrome including all tabs
8. Navigated to facebook.com and twitter.com and observed chrome remember the Username and Password along with the URL accessed. 

dilrajmty@ Could you please confirm is the above steps is the right way to reproduce this issue? If not please feel free to correct me. Could you please explain step-4, I am curious to know how come that the chrome auto fills the password on second URL which was saved from first instance.

Comment 2 by dilraj...@gmail.com, Jan 13 2017 

Hi,
I too dont observe issues while testing with Twitter or Facebook.com. I have noticed issue while testing our software application URL through Chrome.Due to Security reasons I cant reveal the exact URL and credentials. But I can explain the scenario

Let say my website has multiple test environments
Instance 1: xyz1.businessportal.com
User: testuser
Pwd: Password1
Instance 2: xyz2.businessportal.com
User: testuser
Pwd: Password2 (only Pwds changed for diff instance)

Now when I save PWD for Instance 1 and then for instance 2, the remembered pwd is over written. 

Now when I access Instance 1, it autofills the remembered pwd (User: testuser)which is of instance 2. This is incorrect. 

Hope this clarifies.
Project Member

Comment 3 by sheriffbot@chromium.org, Jan 20 2017

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by cda...@chromium.org, Mar 13 2017 

Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919

Comment 5 by cda...@chromium.org, Mar 13 2017

Labels: -Needs-Review

Comment 6 by brajkumar@chromium.org, May 12 2017

Owner: ----
Unable to test this issue without a minimal test case or sample URL, Hence removing myself from the owner field.

Requesting some one from autofill team to look in to this issue.

Thanks!

Comment 7 by ma...@chromium.org, May 1 2018

Status: Untriaged (was: Unconfirmed)
►

Sign in to add a comment