mirror of
https://github.com/docker/docs.git
synced 2026-03-27 14:28:47 +07:00
fix: formatting in admin guides
This commit is contained in:
@@ -18,7 +18,7 @@ Communicate early with users to inform them that:
|
||||
- They'll be upgraded to a supported version of Docker Desktop as part of the subscription onboarding
|
||||
- Settings will be reviewed and optimized for productivity
|
||||
- They'll need to sign in to the company's Docker organization using their
|
||||
business email to access subscription benefits
|
||||
business email to access subscription benefits
|
||||
|
||||
### Engage with your MDM team
|
||||
|
||||
@@ -44,7 +44,7 @@ If you suspect your company has multiple Docker organizations:
|
||||
|
||||
- Survey your teams to see if they have their own organizations
|
||||
- Contact your Docker Support to get a list of organizations with users whose
|
||||
emails match your domain name
|
||||
emails match your domain name
|
||||
|
||||
## Gather requirements
|
||||
|
||||
@@ -60,8 +60,8 @@ configuration:
|
||||
Review these areas together:
|
||||
|
||||
- Security features and
|
||||
[enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md)
|
||||
for Docker Desktop users
|
||||
[enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md)
|
||||
for Docker Desktop users
|
||||
- Additional Docker products included in your subscriptions
|
||||
|
||||
To view the parameters that can be preset, see [Configure Settings Management](/manuals/enterprise/security/hardened-desktop/settings-management/configure-json-file.md#step-two-configure-the-settings-you-want-to-lock-in).
|
||||
|
||||
@@ -7,8 +7,8 @@ weight: 40
|
||||
> [!WARNING]
|
||||
>
|
||||
> Communicate with your users before proceeding, and confirm that your IT and
|
||||
MDM teams are prepared to handle any unexpected issues, as these steps will
|
||||
affect all existing users signing into your Docker organization.
|
||||
> MDM teams are prepared to handle any unexpected issues, as these steps will
|
||||
> affect all existing users signing into your Docker organization.
|
||||
|
||||
## Enforce SSO
|
||||
|
||||
|
||||
@@ -14,23 +14,23 @@ SSO and SCIM setup.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Some users may need CLI based logins to Docker Hub, and for this they will
|
||||
need a [personal access token (PAT)](/manuals/security/access-tokens.md).
|
||||
> need a [personal access token (PAT)](/manuals/security/access-tokens.md).
|
||||
|
||||
## Test Registry Access Management and Image Access Management
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
> Communicate with your users before proceeding, as this step will impact all
|
||||
existing users signing into your Docker organization.
|
||||
> existing users signing into your Docker organization.
|
||||
|
||||
If you plan to use [Registry Access Management (RAM)](/manuals/enterprise/security/hardened-desktop/registry-access-management.md) and/or [Image Access Management (IAM)](/manuals/enterprise/security/hardened-desktop/image-access-management.md):
|
||||
|
||||
1. Ensure your test developer signs in to Docker Desktop using their
|
||||
organization credentials
|
||||
organization credentials
|
||||
2. Have them attempt to pull an unauthorized image or one from a disallowed
|
||||
registry via the Docker CLI
|
||||
registry via the Docker CLI
|
||||
3. Verify they receive an error message indicating that the registry is
|
||||
restricted by the organization
|
||||
restricted by the organization
|
||||
|
||||
## Deploy settings and enforce sign in to test group
|
||||
|
||||
|
||||
@@ -19,11 +19,11 @@ Members are granted controlled access to resources and enjoy enhanced organizati
|
||||
|
||||
### Benefits of inviting members
|
||||
|
||||
- Enhanced visibility: Gain insights into user activity, making it easier to monitor access and enforce security policies.
|
||||
- Streamlined collaboration: Help members collaborate effectively by granting access to shared resources and repositories.
|
||||
- Improved resource management: Organize and track users within your organization, ensuring optimal allocation of resources.
|
||||
- Access to enhanced features: Members benefit from organization-wide perks, such as increased pull limits and access to premium Docker features.
|
||||
- Security control: Apply and enforce security settings at an organizational level, reducing risks associated with unmanaged accounts.
|
||||
- Enhanced visibility: Gain insights into user activity, making it easier to monitor access and enforce security policies.
|
||||
- Streamlined collaboration: Help members collaborate effectively by granting access to shared resources and repositories.
|
||||
- Improved resource management: Organize and track users within your organization, ensuring optimal allocation of resources.
|
||||
- Access to enhanced features: Members benefit from organization-wide perks, such as increased pull limits and access to premium Docker features.
|
||||
- Security control: Apply and enforce security settings at an organizational level, reducing risks associated with unmanaged accounts.
|
||||
|
||||
For detailed information, see [Manage organization members](/manuals/admin/organization/members.md).
|
||||
|
||||
@@ -37,9 +37,9 @@ Integrating Docker with your identity provider streamlines user access and enhan
|
||||
|
||||
SSO:
|
||||
|
||||
- Simplifies sign in, as users sign in with their organizational credentials.
|
||||
- Reduces password-related vulnerabilities.
|
||||
- Simplifies onboarding as it works seamlessly with SCIM and group mapping for automated provisioning.
|
||||
- Simplifies sign in, as users sign in with their organizational credentials.
|
||||
- Reduces password-related vulnerabilities.
|
||||
- Simplifies onboarding as it works seamlessly with SCIM and group mapping for automated provisioning.
|
||||
|
||||
For more information, see the [SSO documentation](/manuals/enterprise/security/single-sign-on/_index.md).
|
||||
|
||||
@@ -49,13 +49,13 @@ Streamline user provisioning and role management with [SCIM](/manuals/enterprise
|
||||
|
||||
With SCIM you can:
|
||||
|
||||
- Sync users and roles automatically with your identity provider.
|
||||
- Automate adding, updating, or removing users based on directory changes.
|
||||
- Sync users and roles automatically with your identity provider.
|
||||
- Automate adding, updating, or removing users based on directory changes.
|
||||
|
||||
With JIT provisioning you can:
|
||||
|
||||
- Automatically add users upon first sign in based on [group mapping](#simplify-access-with-group-mapping).
|
||||
- Reduce overhead by eliminating pre-invite steps.
|
||||
- Automatically add users upon first sign in based on [group mapping](#simplify-access-with-group-mapping).
|
||||
- Reduce overhead by eliminating pre-invite steps.
|
||||
|
||||
### Simplify access with group mapping
|
||||
|
||||
@@ -63,8 +63,8 @@ Group mapping automates permissions management by linking identity provider grou
|
||||
|
||||
It also:
|
||||
|
||||
- Reduces manual errors in role assignments.
|
||||
- Ensures consistent access control policies.
|
||||
- Help you scale permissions as teams grow or change.
|
||||
- Reduces manual errors in role assignments.
|
||||
- Ensures consistent access control policies.
|
||||
- Help you scale permissions as teams grow or change.
|
||||
|
||||
For more information on how it works, see [Group mapping](/manuals/enterprise/security/provisioning/group-mapping.md).
|
||||
|
||||
Reference in New Issue
Block a user