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.

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

Update faq.yml to fix wrong information cloud trust compatibility with RODC #12005

Merged
merged 3 commits into from
Feb 12, 2025

Conversation

ChunlinXuMSFT
Copy link
Contributor

@ChunlinXuMSFT ChunlinXuMSFT commented Feb 11, 2025

as per internal discussion and tests, we confirmed with engineering team there is a known issue between cloud trust and real RODC:

  1. WHfB Cloud trust would only work with RODC if the user’s password can’t be cached by that RODC (as per the password replicdation policy). that is, RODC will to return TGT_Revoked to the client after successfully verifying the partial tgt from WHfB cloud trust client if the user is supposed to have a password cached locally on local RODC.
  2. Auth can be successful if the same RODC has KDC certs and then it can failover to Key trust.

Contact me if any questions.

Why

  • Closes #[Issue Number]

Changes

…h a real RODC

as per internal discussion and tests, we confirmed with engineering team there is a known issue between cloud trust and real RODC:

1.	WHfB Cloud trust would only work with RODC if the user’s password can’t be cached by that RODC (as per the password replicdation policy). that is, RODC will to return TGT_Revoked to the client after successfully verifying the partial tgt from WHfB cloud trust client if the user is supposed to have a password cached locally on local RODC.
2.	Auth can be successful if the same RODC has KDC certs and then it can failover to Key trust.
Copy link
Contributor

Learn Build status updates of commit 5ea3075:

✅ Validation status: passed

File Status Preview URL Details
windows/security/identity-protection/hello-for-business/faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@paolomatarazzo paolomatarazzo self-assigned this Feb 11, 2025
Copy link
Contributor

Learn Build status updates of commit 60df47a:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
windows/security/identity-protection/hello-for-business/faq.yml ❌Error Details

windows/security/identity-protection/hello-for-business/faq.yml

  • Line 215, Column 9: [Error: yaml-syntax-error - See documentation] While parsing a block mapping, did not find expected key.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Copy link
Contributor

Learn Build status updates of commit 494304b:

✅ Validation status: passed

File Status Preview URL Details
windows/security/identity-protection/hello-for-business/faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@paolomatarazzo paolomatarazzo merged commit 7ab3b71 into MicrosoftDocs:public Feb 12, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants