Conversation
|
|
||
|  | ||
|
|
||
| > Note: If the uploaded profile is signed, Fleet will replace the variables and invalidate the signature. |
There was a problem hiding this comment.
This is why we should be signing configuration profiles on the server side.
|
The example provided is for a legacy configuration profile. We should consider including steps for a DDM certificate profile. DDM does not currently support network configurations, which must be wrapped in a legacy profile. |
The customer is currently using legacy profile and the current implementation doesn't support DDM/Windows profiles. @noahtalerman should we have a story for DDM/Windows support or is that part of #13420 -- not sure about the new flow |
@getvictor I just added this above the fold in the "Help end users connect to Wi-Fi with certificates" feature request (just updated the title):
In progress PR for the new flow is here: https://github.com/fleetdm/fleet/pull/23019/files |
|
@getvictor I think let's add a sentence about the variables supported by default and to use them: https://support.apple.com/en-gb/guide/deployment/dep04666af94/1/web/1.0 Or, even easier, we could link to this guide which already points to the above Apple link. What do you think? |
@noahtalerman sentence/link added |
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>


For Fleet v4.59.0 release #21955