commit | 522851984a66c9c4a63815fd9c93d5a9c902d1df | [log] [tgz] |
---|---|---|
author | Jood <jood@google.com> | Tue Dec 17 14:15:27 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 17 14:15:27 2024 |
tree | 97070490cee01fa27344f3fad27dc6d10f89e4b0 | |
parent | aec67a3560373bcf47bdbfba993d3331267a149c [diff] |
[iOS] Introduce signout helper in signin_utils to support multi profile For managed accounts, with multi profiles introduced, the sign out flow should change to, first, switch to the default (personal) profile, then bring it to a signed-out state. This is required as managed profiles should only be in a signed-in state. To achieve that, this CL: * introduces a multi profile sign-out helper in signin_utils, to decide if a profile switch is needed and execute it * the profile switch is done using ChangeProfileCommands * the helper uses ChangeProfileSignoutContinuation (see crrev.com/c/6088919) to trigger the sign-out action after a successful profile switch. And even if no switch was done, in order to support the current flows that will be migrated in later CLs. * lastly, exposes GetPersonalProfileName in AccountProfileMapper Later CLs will implement the sign-out, and will migrate all AuthenticationService::SignOut callers to use these helpers. Bug: 375605174 Change-Id: I32032e4933a6721d20a9152f76d472e259fbaf6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6085258 Reviewed-by: Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Jood Hajeer <jood@google.com> Cr-Commit-Position: refs/heads/main@{#1397281}
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.