Dumping the AD for import into Bloodhound fails using low priv. accounts in 2.0.4

[jsdhasfedssad]

I can successfully dump my AD for import into Bloodhound using 2.0.1 and a low .priv account.

When I try this in 2.0.4 using the same low priv. account as above and the same AD this partially fails.

When I use the account domainadmin1 (high priv.) dumping works in 2.0.4.

Is all of this intentionally? If not something seems to have broken.

[ly4k]

I changed the method for retrieving the CA configuration from Remote Registry (MS-RRP) to Certificate Services Remote Administration (MS-CSRA). During my own testing, I found that low privileged users could retrieve the configuration from MS-CSRA, but it might be because you're missing the CERTSVC_DCOM_ACCESS group membership, and as such, you cannot connect via DCOM. Perhaps remote registry is better after all, and maybe MS-CSRA as fallback. Will fix this later today. Thanks for reporting the issue

[ly4k]

Should be fixed in 2.0.5. Can you please verify?

[jsdhasfedssad]

Great! Assuming the error below is just temporary until the backup feature runs, this works in 2.0.6.

[ly4k]

Yes, so the new version tries both methods. The MS-CSRA method is faster when the Remote Registry service isn't running, but apparently that method behaves differently in regards to permissions, probably because of DCOM. So yes, the output is a bit verbose if MS-CSRA fails. Perhaps I could print it only in verbose (-debug) mode :)