[SAML] Add SamlRedirect to Gaia paths and improve tests

Handle "samlredirect" Gaia path the same way as other Gaia paths used by
ChromeOS and start checking it in some SAML tests.

Details:
- GaiaUrls now knows about "samlredirect" Gaia path
- kSamlRedirect is added to WizardContext::GaiaPath enum and it is now
respected by GaiaScreen and GaiaScreenHandler
- "samlredirect" is now passed as a "gaiaPath" from
GaiaScreenHandler/LockScreenHandler to JS code. In particular,
"samlredirect" is no longer hardcoded in authenticator.js
- Implementation of "Enter Google Account Info" button had to be
changed: previously it relied on the fact that "gaiaPath" pointed to a
default Gaia sign-in page, now there is a separate "fallbackGaiaPath"
parameter passed from C++ for this button (both on the login screen and
on the lock screen)
- Several SAML tests now verify the Gaia path used by the Gaia screen.
- New test SamlReauthWithSamlRedirect tests reauth flow for SAML user
with LoginAuthenticationBehavior policy set to navigate directly to SAML
page
- SAMLPolicyTest methods which update policies now correctly wait for
corresponding CrosSettings to update. This restores the behavior which
was mistakenly removed during refactoring in
https://crrev.com/c/4489824.

Bug: b:309148088, b:287922689
Change-Id: Icac9abae601802a31453667b517d225def1e612a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5007622
Commit-Queue: Andrey Davydov <andreydav@google.com>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Reviewed-by: Mohammed Abdon <mohammedabdon@chromium.org>
Reviewed-by: Danila Kuzmin <dkuzmin@google.com>
Cr-Commit-Position: refs/heads/main@{#1221566}
13 files changed
tree: 91237a103a4abb7bbc6d07e1ab7558520f19f428
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

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.