[Security] Updates docs for enabling Defend access on macOS #2396
Conversation
|
|
There was a problem hiding this comment.
I think you can remove these files with the real redirections that you added to the redirects.yml file
Edit: Seeing the automatic comment, I'm not sure , but I thought the redirects system was complete 😅
There was a problem hiding this comment.
I initially removed them and got this message, so I followed what it said 🤷♀️
There was a problem hiding this comment.
I can go back and remove them again, but do we have any guidance on when we should remove them vs keep them as hidden?
There was a problem hiding this comment.
Yeah, noticed this afterwards
There was a problem hiding this comment.
Maybe @elastic/docs-engineering could help confirm the right action here? :)
There was a problem hiding this comment.
I am probably wrong here, better follow the guidance in the auto-comment
| 4. Enter your username and password and click **Modify Settings** to save your changes. | ||
| ::: | ||
|
|
||
| :::{tab-item} Monterey (12.x) |
There was a problem hiding this comment.
You may want to use :group: and :sync: props so that all of the same items in other sections are also selected when the user clicks
There was a problem hiding this comment.
Nice, that's a cool feature 🚀
Resolves #2101 by adding instructions for approving the
ElasticEndpointsystem extension for macOS Sequoia.Instead of creating a new page for macOS Sequoia, I consolidated the existing instructions for Monterey and Ventura with the new instructions for Sequoia into a single page using tabs, since the differences are minimal.
For the removed pages (Enable access for macOS Monterey and Enable access for macOS Ventura and higher), I've changed them to "hidden" in the TOC, replaced the content with a "This page has moved" note, and created redirects in the redirect.yml file.
Previews:
Removed pages: