Skip to content

SAP Diag/RFC: Add Extended Passport support across SAP protocols - #107

Merged
martingalloar merged 1 commit into
OWASP:masterfrom
martingalloar:epp
Sep 15, 2026
Merged

martingalloar merged 1 commit into
OWASP:masterfrom
martingalloar:epp

Conversation

@martingalloar

Copy link
Copy Markdown
Collaborator
  • model EPP versions 1–3, variable parts, and items
  • add SAP-PASSPORT HTTP header conversion helpers
  • decode EPP in SAP Diag, classic RFC, and NWRFC
  • replace incompatible SAPRFCTHStruct with SAPEPP
  • add RFCID constants and bounded NI streaming
  • document the new APIs and breaking change

- model EPP versions 1–3, variable parts, and items
- add SAP-PASSPORT HTTP header conversion helpers
- decode EPP in SAP Diag, classic RFC, and NWRFC
- replace incompatible SAPRFCTHStruct with SAPEPP
- add RFCID constants and bounded NI streaming
- document the new APIs and breaking change
@martingalloar martingalloar self-assigned this Sep 15, 2026
@martingalloar
martingalloar merged commit 436c9de into OWASP:master Sep 15, 2026
16 checks passed
@martingalloar
martingalloar deleted the epp branch September 15, 2026 05:06
@joegoerlich

Copy link
Copy Markdown

@martingalloar I believe the differentiation between classic RFC and NWRFC would also be something worth to contribute to the SAP Dissector in Wireshark to identify whether the traffic is from an 3rd party interface or native ABAP. What's your thought about that?

@martingalloar

Copy link
Copy Markdown
Collaborator Author

Yes, 100%! I've just added standard support of EPP in Diag and classic RFC but will be looking to support NWRFC into Wireshark as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants