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

Password hash synchronization and FIPS: workaround fails #60306

Closed
A9G-Data-Droid opened this issue Aug 5, 2020 · 4 comments
Closed

Password hash synchronization and FIPS: workaround fails #60306

A9G-Data-Droid opened this issue Aug 5, 2020 · 4 comments

Comments

@A9G-Data-Droid
Copy link

We are unable to run Azure-AD connect with FIPS mode on. The workaround cited on this page isn't working. Sync still fails until FIPS mode is disabled on the system. This is an unacceptable solution.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@MarileeTurscak-MSFT
Copy link
Contributor

@A9G-Data-Droid
Thanks for your feedback! We will investigate and update as appropriate.

@amicone
Copy link

amicone commented Oct 27, 2020

Adding additional information: Not only does the change for FIPS compliance not work, but the documentation is also incorrect. The miiserver.exe.config is not stored relative to %programfiles%, it is stored relative to the data storage directory chosen during AD Connect installation.

@billmath
Copy link
Contributor

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close

@A9G-Data-Droid
Copy link
Author

The documentation is wrong and needs to be edited. The whole section "Password hash synchronization and FIPS" needs to be edited or removed. It's both technically wrong and doesn't work.

You also failed to fill in the critical detail of your canned message:

redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint].

That's where you are supposed to put something helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants