Skip to content

Commit eabe758

Browse files
authored
enforce sign-in caps (#25033)
<!--Delete sections as needed --> ## Description Closes #24953 Closes #24942 ## Related issues or tickets <!-- Related issues, pull requests, or Jira tickets --> ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review
1 parent 04825ca commit eabe758

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

  • content/manuals/enterprise/security/enforce-sign-in

content/manuals/enterprise/security/enforce-sign-in/methods.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Configuration profiles provide the most secure enforcement method for Mac, as th
7676

7777
The payload is a dictionary of key-values. Docker Desktop supports the following keys:
7878

79-
- `allowedOrgs`: Sets a list of organizations in one single string, where each organization is separated by a semi-colon.
79+
- `allowedOrgs`: Sets a list of organizations in one single string, where each organization is in lowercase only and is separated by a semi-colon.
8080
- `overrideProxyHTTP`: Sets the URL of the HTTP proxy that must be used for outgoing HTTP requests.
8181
- `overrideProxyHTTPS`: Sets the URL of the HTTP proxy that must be used for outgoing HTTPS requests.
8282
- `overrideProxyExclude`: Bypasses proxy settings for the specified hosts and domains. Uses a comma-separated list.
@@ -108,7 +108,7 @@ Overriding at least one of the proxy settings via Configuration profiles will au
108108
<key>PayloadDescription</key>
109109
<string>Configuration profile to manage Docker Desktop settings.</string>
110110
<key>PayloadOrganization</key>
111-
<string>Your Company Name</string>
111+
<string>Your company name</string>
112112
<key>allowedOrgs</key>
113113
<string>first_org;second_org</string>
114114
<key>overrideProxyHTTP</key>
@@ -130,13 +130,13 @@ Overriding at least one of the proxy settings via Configuration profiles will au
130130
<key>PayloadDescription</key>
131131
<string>Config profile to enforce Docker Desktop settings for allowed organizations.</string>
132132
<key>PayloadOrganization</key>
133-
<string>Your Company Name</string>
133+
<string>Your company name</string>
134134
</dict>
135135
</plist>
136136
```
137137
1. Replace placeholders:
138138
- Change `com.yourcompany.docker.config` to your company identifier
139-
- Replace `Your Company Name` with your organization name
139+
- Replace `Your company name` with your organization name making sure it is all lowercase
140140
- Replace `PayloadUUID` with a randomly generated UUID
141141
- Update the `allowedOrgs` value with your organization names (separated by semicolons)
142142
- Replace `company.proxy:port` with http/https proxy server host(or IP address) and port
@@ -162,7 +162,7 @@ Some MDM solutions let you specify the payload as a plain dictionary of key-valu
162162
{{< tab name="Manual creation" >}}
163163

164164
1. Create the file `/Library/Application Support/com.docker.docker/desktop.plist`.
165-
1. Add this content, replacing `myorg1` and `myorg2` with your organization names:
165+
1. Add this content, replacing `myorg1` and `myorg2` with your organization names and making sure they have lowercase letters only:
166166
```xml
167167
<?xml version="1.0" encoding="UTF-8"?>
168168
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
@@ -225,7 +225,7 @@ Create the `registry.json` file (UTF-8 without BOM) at the appropriate location:
225225

226226
1. Ensure users are members of your Docker organization.
227227
1. Create the `registry.json` file at the appropriate location for your platform.
228-
1. Add this content, replacing organization names with your own:
228+
1. Add this content, replacing organization names with your own and making sure they have lowercase letters only:
229229
```json
230230
{
231231
"allowedOrgs": ["myorg1", "myorg2"]

0 commit comments

Comments
 (0)