BED-5562 changing LDAP InvalidOperationException to debug #202
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Linked to SpecterOps/SharpHound#141 |
definitelynotagoblin
approved these changes
May 14, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changing LDAP InvalidOperationException to debug
Motivation and Context
https://specterops.atlassian.net/browse/BED-5562
Resolves SpecterOps/SharpHound#141
How Has This Been Tested?
Run a SharpHound collection and check the service.log that the error below does not appear
|ERROR|An unhandled error occurred during the LDAP test: System.InvalidOperationException: Server did return a challengeScreenshots (if appropriate):
Types of changes
Checklist: