Skip to content

Commit c61f0a5

Browse files
paulOsinskiPaul Osinski
and
Paul Osinski
authored
Pro Release notes : 2.44.1 (#11983)
* update changelog 2.44 * 2.44.1 release notes --------- Co-authored-by: Paul Osinski <[email protected]>
1 parent 7d3106e commit c61f0a5

File tree

3 files changed

+21
-2
lines changed

3 files changed

+21
-2
lines changed

docs/assets/images/odic.png

64.8 KB
Loading

docs/content/en/changelog/changelog.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,20 @@ For Open Source release notes, please see the [Releases page on GitHub](https://
1010

1111
## Mar 2025: v2.44
1212

13+
### Mar 10, 2025: v2.44.1
14+
15+
- **(Beta UI)** Added a field in the View Engagement page which allows a user to navigate to the linked Jira Epic, if one exists.
16+
- **(Universal Parser)** XML is now a supported file type for Universal Parser.
17+
- **(SSO)** SSO can now be set up with any kind of [OIDC Configuration](https://auth0.com/docs/authenticate/protocols/openid-connect-protocol). See ODIC Settings in the Beta UI:
18+
19+
![image](images/odic.png)
20+
21+
### Mar 3, 2025: v2.44.0
22+
23+
- **(Beta UI)** Breadcrumbs have been overhauled to better represent the context each page exists in. Breadcrumbs will now include filtering and query parameters. The titles of tables now better represent their context, for example when looking at the Engagements list for a particular Product, the view will be titled {Product Name} Engagements, rather than All Engagements as before.
24+
25+
## Mar 2025: v2.44
26+
1327
### Mar 3, 2025: v2.44.0
1428

1529
- **(Beta UI)** Breadcrumbs have been overhauled to better represent the context each page exists in. Breadcrumbs will now include filtering and query parameters. The titles of tables now better represent their context, for example when looking at the Engagements list for a particular Product, the view will be titled {Product Name} Engagements, rather than All Engagements as before.

docs/content/en/connecting_your_tools/universal_parser.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,16 @@ pro-feature: true
1010

1111
The Universal Parser is currently in Beta. See our [announcement presentation](https://community.defectdojo.com/universalparser) for more information.
1212

13+
## About Universal Parser
14+
DefectDojo has a large, regularly updated library of parsers to help security teams ingest data. However, sometimes users have a tool that's unsupported by the parsers, or they may want to import data into the DefectDojo model differently from the way the parser does.
15+
16+
DefectDojo's Universal Parser is meant to give our users with unsupported report types a path forward, to import and map **any JSON, CSV or XML file**.
17+
1318
**The Universal Parser is:**
1419

1520
* A quick way to support file formats for which we do not have Community parsers, such as reports produced by internal tools
16-
* A tool to help you ingest data even if a Community parser is out-of-date or doesn't structure findings the way you would like
17-
* An alternative to custom scripting that transforms tool reports into the CSV/JSON format expected by the "Generic Findings Import" scan type
21+
* A tool to help you ingest data, even if a Community parser is out-of-date or doesn't structure findings the way you would like
22+
* An alternative to custom scripting to transform tool reports into the CSV/JSON format expected by the "Generic Findings Import" scan type
1823
* Designed to be easy to use for anyone, with no coding and minimal configuration required
1924

2025
**The Universal Parser is not:**

0 commit comments

Comments
 (0)