fix: app scoped role assignment not properly linking to AZApp #78
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.
BED-4348
Adds workaround handling for app specific scoped role assignments. This ensures that downstream ingestion by Bloodhound will add edge to correct
AZApp
nodeImplementation
Expanded
directoryScope
inListAzureADRoleAssignments
which provides theappId
of the scoped app.Hotswapped that in place for the
directoryScopeId
to be consumed downstream.No changes needed to Bloodhound.
Testing
Ran collection locally pointing at Azure env with role assignment scoped to specific app and ensured that it was properly linked in Bloodhound.
Query:
MATCH p = (:AZUser)-[:AZAppAdmin]->()