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

[backend] Improve config restrictions / visibility for batch rel loading #6473

Merged
merged 2 commits into from Mar 30, 2024

Conversation

richard-julien
Copy link
Member

Different improvements out of the milestone.

  • Better restrictions for logsWorkerConfig api
  • Adapt restrictions for work management + wrap security in the UI
  • Remove unneeded node sharing in rabbitMQ OverviewMetrics

@richard-julien richard-julien added the filigran team use to identify PR from the Filigran team label Mar 26, 2024
@richard-julien richard-julien self-assigned this Mar 26, 2024
Copy link

codecov bot commented Mar 26, 2024

Codecov Report

Attention: Patch coverage is 60.86957% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 67.65%. Comparing base (008b6b7) to head (98bdb8a).

Files Patch % Lines
...tform/opencti-graphql/src/domain/stixCoreObject.js 60.86% 9 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6473      +/-   ##
==========================================
- Coverage   67.65%   67.65%   -0.01%     
==========================================
  Files         532      532              
  Lines       65001    65017      +16     
  Branches     5434     5437       +3     
==========================================
+ Hits        43979    43988       +9     
- Misses      21022    21029       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

return resolve;
}
// If access is not possible, return a restricted entity
return { id: resolve.internal_id, name: 'Restricted', entity_type: resolve.entity_type };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible for a given entity_type to NOT have a name attribute, leading to an impossible object schema-wise ? an opinion for instance.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the same issue in my PR #6323

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed, if you're confident it concerns only entities with names, let's go for it as it would not be disruptive for the frontend side.

@SamuelHassine SamuelHassine merged commit 5ff2123 into master Mar 30, 2024
10 checks passed
@SamuelHassine SamuelHassine deleted the oob/api_protection branch March 30, 2024 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants