Increase the threshold for UploadDeviceDetails failures. When UploadDeviceDetails is called during a reauth logon, we write the status (failure or success) and the number of times it failed to the registry. When checking if the user needs to reauth or not, if the registry values indicate failure and it failed less times than this value, a reauth is forced. But to avoid bothering the user with constant reauths, if UploadDeviceDetails keeps failing on every reauth, and if failed more than n times, we skip forcing the reauth from then on. Increase this number from 3 to 7 in the hopes that UploadDeviceDetails finally succeeds, so the dm_token generated with GenerateGCPWDmToken is uploaded to avoid some authentication failures happening in the GCPW Extension http requests. Change-Id: Iea0bdd84bf55463b682e6de59ae63ea255519daf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6111820 Reviewed-by: Yusuf Sengul <yusufsn@google.com> Reviewed-by: Rakesh Soma <rakeshsoma@google.com> Commit-Queue: Rakesh Soma <rakeshsoma@google.com> Cr-Commit-Position: refs/heads/main@{#1427558}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.