Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix docs build #327

Merged
merged 2 commits into from
Jun 5, 2024
Merged

Fix docs build #327

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ac0f275
Fix docs build
tashian Jun 5, 2024
cfca354
Update platform/README.mdx
tashian Jun 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 6 additions & 12 deletions platform/README.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,18 +64,12 @@ See:

<Alert severity="info">
<div>
💡 What about MDM’s that do not support Dynamic SCEP?
<p>
There are two main approaches to using SCEP as a certificate enrolment protocol: static and dynamic.
</p>
<p>
In static SCEP, a single challenge password is in every SCEP payload for every device. This practice is insecure and not recommended. Furthermore, it only shows a single user in reporting. We do not support this because we believe it's crucial to provide the most secure options for your infrastructure.
</p>
<p>
In contrast, for Dynamic SCEP, webhooks are used to generate new challenges and unique passwords for each device, and you would be able to see reporting for all devices.
</p>
<p>In such a case where your MDM does not support Dynamic SCEP, your next best bet to deploy Smallstep is to use the Smallstep Agent. <em> See details below </em>
</p>
<p><strong>💡 What about MDM’s that do not support Dynamic SCEP? </strong></p>
<p>There are two main approaches to using SCEP as a certificate enrollment protocol: static and dynamic. </p>

<p>In static SCEP, a single challenge password is in every SCEP payload for every device. This practice is insecure and not recommended. Furthermore, it only shows a single user in reporting. We do not support this because we believe it's crucial to provide the most secure options for your infrastructure.</p>
<p>In contrast, for Dynamic SCEP, webhooks are used to generate new challenges and unique passwords for each device, and you would be able to see reporting for all devices.</p>
<p>If your MDM does not support Dynamic SCEP, your next best bet to deploy Smallstep is to use the Smallstep Agent. <em>See details below.</em></p>
</div>
</Alert>

Expand Down