tree: 83a16cda55eb8374634605f9b5f596f13e281993 [path history] [tgz]
  1. multi_user/
  2. user_image/
  3. account_id_util.cc
  4. account_id_util.h
  5. account_id_util_unittest.cc
  6. BUILD.gn
  7. common_types.h
  8. DEPS
  9. device_ownership_waiter.h
  10. device_ownership_waiter_impl.cc
  11. device_ownership_waiter_impl.h
  12. device_ownership_waiter_unittest.cc
  13. DIR_METADATA
  14. fake_device_ownership_waiter.cc
  15. fake_device_ownership_waiter.h
  16. fake_user_manager.cc
  17. fake_user_manager.h
  18. fake_user_manager_delegate.cc
  19. fake_user_manager_delegate.h
  20. include_exclude_account_id_filter.cc
  21. include_exclude_account_id_filter.h
  22. include_exclude_account_id_filter_unittest.cc
  23. known_user.cc
  24. known_user.h
  25. known_user_unittest.cc
  26. OWNERS
  27. README.md
  28. scoped_user_manager.cc
  29. scoped_user_manager.h
  30. user.cc
  31. user.h
  32. user_directory_integrity_manager.cc
  33. user_directory_integrity_manager.h
  34. user_manager.cc
  35. user_manager.h
  36. user_manager_base.cc
  37. user_manager_base.h
  38. user_manager_export.h
  39. user_manager_pref_names.h
  40. user_names.cc
  41. user_names.h
  42. user_type.cc
  43. user_type.h
  44. user_unittest.cc
components/user_manager/README.md

UserManager

This directory contains files for managing ChromeOS users. Historically, the code manages both user and user sessions. There is an on-going effort to move user session related code into //components/session_manager.

UserManager is the interface for managing ChromeOS users. UserManagerBase is a base implementation of the interface. Finally, the concrete instance used is ChromeUserManagerImpl derived from UserManagerBase.

ChromeUserManagerImpl is created at the PreProfileInit stage and destroyed at the PostMainMessageLoopRun stage, via BrowserProcessPlatformPart::InitializeUserManager() and BrowserProcessPlatformPart::DestroyUserManager.

UserDirectoryIntegrityManager

This directory contains the UserDirectoryIntegrityManager class. This class is responsible for detecting when a user did not completely complete the onboarding flow and crashed before adding an auth factor. This can leave the user in an inconsistent state as their home directory will be encrypted with no auth factors added.

UserDirectoryIntegrityManager writes the user's email to local state before creating the user home directory and erases it after adding a successful auth factor. Those operations are initiated from MountPerformer::CreateNewUser and AuthFactorEditor::OnAddCredentials respectively.

design doc