-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add MART reports importer #5032
base: main
Are you sure you want to change the base?
Add MART reports importer #5032
Conversation
318d11c
to
8890569
Compare
50c3553
to
a8ba7d0
Compare
a8ba7d0
to
91ba896
Compare
eb13870
to
e47948d
Compare
e47948d
to
a75589f
Compare
Show a nice icon indicating import success status. Add missing avatar to person link. Simplify code. Remove unnecessary Component prop.
Also use "boolean" type as everywhere else.
Delete imported reports, thus fixing MartImportedReportsResourceTest. Properly report MART import errors as a list.
SnakeYAML 2.3 has a bug while reading a YAML file: when the last character in the buffer is a multi-byte Unicode character, it may fail with: java.lang.ArrayIndexOutOfBoundsException: Index 1024 out of bounds for length 1024 It will be fixed in 2.4, but that hasn't been released yet, so simply replace the Unicode character by some text.
e699b63
to
42dfd08
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, we test in the Azure testbed after merging
anetReport.setIntent(martReport.getIntent()); | ||
anetReport.setEngagementDate(martReport.getEngagementDate()); | ||
anetReport.setReportText(martReport.getReportText()); | ||
anetReport.setClassification("NKU"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be hard-coded. Instead it should come from the report (there's a custom field called securityMarking
that should contain the correct value). Site admins need to make sure that both sides have this marking in their configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @gjvoosten, we need to read the security marking preferably from the report, alternatively from the dictionary. But hard coding it to a value with is already configured in the dictionary, is not very solid.
Implementation of a MART reports importer and an admin GUI to monitor it.
Closes AB#1011
User changes
Superuser changes
Admin changes
System admin changes
Update
application.yml
:Checklist
repo#issue: Title
title format and these 7 rules