SAP / SAP/openapi-specification
SAP Integration Cell – OpenAPI extension properties outside of SAP's registered namespace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
When creating an API in SAP Integration Suite for the Integration Cell runtime, the resulting OpenAPI specification reveals that SAP uses OpenAPI extension properties outside its registered namespace.
For example:
x-apiProviderx-relativeUrl
This is a bug waiting to happen because customers will experience name collisions once a backend API happens to ship with extension properties like e.g. x-apiProvider.
I have also raised SAP case 1005066/2026 on that matter.
Please reach out to product management for SAP Integration Suite, API Management to get this fixed.
Thank you
Michael
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the reported OpenAPI extension properties x-apiProvider and x-relativeUrl against SAP's registered namespace and the OpenAPI specification-extensions guidance linked in the issue. Confirm the required namespace change with product management for SAP Integration Suite, API Management; done means the generated specification no longer uses unregistered extension names and the affected properties are covered by SAP's namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, typescript
- Domain
- api, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100