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

Issue 639767 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome does not store any passwords (localy) and the autofill funktion does not work. A sychronization is not possible with the google server

Reported by a...@pixum.com, Aug 22 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Installing or upgrading a Windows computer (in our case form Windows7) to Windows10 and integrating the computer to our local domain
2. Creating a new windows domain user account under Windows10
3. Using a existing or a new G-Mail account and trying to store passwords in Chrome and afterwards trying to synchronize the passwords with the google server

What is the expected behavior?
- Chrome will ask if the passwords should be stored, our users do want to use this function
- After storing the passwords localy a synchronnization with the google server should be possible

What went wrong?
- The list of stored passwords remains empty and Chrome just does not write any data in: C:\Users\yourUser\AppData\Local\Google\Chrome\User Data\Default  in the file "Login Data" the size of the file remains the same
- Windows domain users whose windows accounts have been created under Windows7 have no problems after the update Win7 to Win10. Only if they login in another computer an create a new domain-local windows account, they won't be able to synchronize their passwords in the new computer or to store new passwords in chrome, only their bookmarks will be inmported

Did this work before? No 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

- As domain controller we use a Linux Debian / Samba4 Server
-troubleshooting: 
-- All synchronisation function known to us are activated (Password storing, cookies enabled storing for local data)
-- Rename o delete the chrome profile, in order hat chrome creates a new one
-- Reinstallation of the complete OS Windows10
-- Deinstalltion and reinstallation of Chrome
-- deleting several times the cookies and browser data
-- Other browsers do not seem to have this essue, as Firefoy stores everithing  
-- Local windpows accounts(no domain users) do not have the problem
-- All our users have administrator account in all machines
 

Comment 1 by a...@pixum.com, Aug 22 2016

Users who have the problem, get the error message: "The loin data for the account are too old, please do the login again" (tranlated form German), every time thy do the login process and closing an reopening chrome

Comment 2 by pav...@chromium.org, Aug 22 2016

Components: Services>SignIn
Labels: Needs-Feedback
ada@: 
To ensure that you are signed in could you open about:chrome-signin and enter your email and password. 
After you go through signin flow could you take a screenshot of about:signin-internals and post it here.

Comment 3 by a...@pixum.com, Aug 23 2016

Hello,
hoppe I got you write.
Thank you for comments / corrections :-)
signed in.JPG
85.7 KB View Download

Comment 4 by pav...@chromium.org, Aug 24 2016

Components: UI>Browser>Passwords
Adding passwords team.

ada@: Could you take a screenshot of about:sync-internals and post it here?

Comment 5 by a...@pixum.com, Aug 25 2016

sycinternals.zip
526 KB Download

Comment 6 by pav...@chromium.org, Aug 25 2016

Cc: vasi...@chromium.org
Labels: Sync-Triaged
Information from about:sync shows that user is signed in and sync is healthy. Passwords datatype is enabled, there are 30 passwords synced to client.

The issue could be in password_manager component.
Cc: wfh@chromium.org
Looks like something with the passwords encryption. May be this is relevant https://productforums.google.com/forum/#!topic/chrome/dPMyABwLV0g ?

Comment 8 by a...@pixum.com, Aug 29 2016

Thank you so much, the issue is resolved!
Status: WontFix (was: Unconfirmed)

Sign in to add a comment