Skip to content

Add 'Additional Notes' for NTLM Block error #6916

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vbrennydossa
Copy link

When the certificate replacement is executed by an account that is member of 'Protected Users', the NTLM authentication is blocked (and it's used by the replacement). This is documented in the Protected Users page, but not in the certificate replacement page. Currently, the only occurrence of the scenario is under a forum post. Updating here because it would have saved me 3 days of troubleshooting in a recent case, and may save others :)

When the certificate replacement is executed by an account that is member of 'Protected Users', the NTLM authentication is blocked (and it's used by the replacement). This is documented in the Protected Users page, but not in the certificate replacement page. Currently, the only occurrence of the scenario is under a forum post. 
Updating here because it would have saved me 3 days of troubleshooting in a recent case, and may save others :)
@prmerger-automator
Copy link
Contributor

@vbrennydossa : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jenfieldmsft

@opbld32
Copy link

opbld32 commented Dec 13, 2022

Learn Build status updates of commit 79ec54e:

✅ Validation status: passed

File Status Preview URL Details
WindowsServerDocs/identity/ad-fs/operations/manage-ssl-certificates-ad-fs-wap.md ✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@Jak-MS
Copy link
Contributor

Jak-MS commented Dec 16, 2022

#assign: @robinharwood, @Xelu86

Can you review the proposed changes? New content should be submitted via the private repo to benefit from staging, validation, and Acrolinx checks. Let us know if you'd like assistance with moving the commits into the private repo.
Note that the file name needs to be revised to meet the file naming guidelines and the new article should be added to a TOC.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator
Copy link
Contributor

The following users don't have valid GitHub IDs, or are not collaborators on this repo: robinharwood xelu86

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Dec 16, 2022
learn-build-service-prod bot pushed a commit that referenced this pull request Apr 23, 2025
Freshness pass: Group Policy overview
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants