Enterprise docs: Replace links with p-links
The presubmit told me so. TBR=rsorokin@chromium.org BUG=b/138287069 TEST=None Change-Id: I6e32ff7e4cc74e044e949e09a75d8fffbd271c5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731835 Reviewed-by: Lutz Justen <ljusten@chromium.org> Commit-Queue: Lutz Justen <ljusten@chromium.org> Cr-Commit-Position: refs/heads/master@{#683505}
This commit is contained in:
@@ -7,9 +7,9 @@ credentials. Admins manage sessions and push policies to users and devices from
|
|||||||
their AD servers using group policy. There is no need to synchronize users to
|
their AD servers using group policy. There is no need to synchronize users to
|
||||||
Google.
|
Google.
|
||||||
|
|
||||||
[Google Chrome Enterprise Help article](https://support.google.com/chrome/a/answer/7497916)
|
[Google Chrome Enterprise Help article](https://support.google.com/chrome/a?p=ad)
|
||||||
|
|
||||||
[Troubleshoot Active Directory](https://support.google.com/chrome/a/answer/7497305)
|
[Troubleshoot Active Directory](https://support.google.com/chrome/a?p=troubleshoot_ad)
|
||||||
|
|
||||||
[TOC]
|
[TOC]
|
||||||
|
|
||||||
@@ -73,7 +73,7 @@ the content area.
|
|||||||
|
|
||||||
Moreover, users may sign up for a Play Store account from within their user
|
Moreover, users may sign up for a Play Store account from within their user
|
||||||
session, see step 5 of the
|
session, see step 5 of the
|
||||||
[Help article](https://support.google.com/chrome/a/answer/7497916).
|
[Help article](https://support.google.com/chrome/a?p=ad).
|
||||||
For this purpose, DM Server creates a LaForge account for the user. A LaForge
|
For this purpose, DM Server creates a LaForge account for the user. A LaForge
|
||||||
account is a shadow Gaia account with scope limited to the Play Store. To prove
|
account is a shadow Gaia account with scope limited to the Play Store. To prove
|
||||||
the user's identity, a SAML flow is employed with DM Server as service provider
|
the user's identity, a SAML flow is employed with DM Server as service provider
|
||||||
|
@@ -35,7 +35,7 @@ On these systems it is also possible to set machine-wide cloud-based policies.
|
|||||||
** Chrome OS **
|
** Chrome OS **
|
||||||
|
|
||||||
Chrome OS devices can be either cloud-managed or Active Directory managed
|
Chrome OS devices can be either cloud-managed or Active Directory managed
|
||||||
([AdManagement](https://support.google.com/chrome/a/answer/7497916?hl=en)).
|
([AdManagement](https://support.google.com/chrome/a?p=ad)).
|
||||||
|
|
||||||
The cloud source is usually called DMServer (device management server).
|
The cloud source is usually called DMServer (device management server).
|
||||||
Organization admins can configure both device and cloud policies using
|
Organization admins can configure both device and cloud policies using
|
||||||
|
@@ -14,7 +14,7 @@ Some enterprises use a more sophisticated model where authentication is handled
|
|||||||
by a third-party IdP (identity provider). GAIA supports this model via the
|
by a third-party IdP (identity provider). GAIA supports this model via the
|
||||||
industry-standard
|
industry-standard
|
||||||
[SAML protocol](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language).
|
[SAML protocol](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language).
|
||||||
A domain can be [configured](https://support.google.com/a/answer/6349809) to
|
A domain can be [configured](https://support.google.com/a?p=sso) to
|
||||||
use SAML authentication.
|
use SAML authentication.
|
||||||
|
|
||||||
## Obtaining the user’s password
|
## Obtaining the user’s password
|
||||||
|
Reference in New Issue
Block a user