8000 API ML not passing HTTPS JES2EDS notifications · Issue #3096 · zowe/api-layer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
API ML not passing HTTPS JES2EDS notifications #3096
Closed as not planned
Closed as not planned
@Destabilizator

Description

@Destabilizator

Describe the bug
Submit job via z/OSMF zJobs API (https://www.ibm.com/docs/en/zos/2.5.0?topic=interface-submit-job) and utilize X-IBM-Notification-URL header which points to app sitting behind API ML and listening for inbound notifications.
According to z/OS logs, the secure transport is successfully negotiated (JES2 cert was added to API ML keystore and AT-TLS policy defined) and notification is sent, but nothing arrives to the app.
Launching a simple HTTPS server using the same certificates as the app works fine.

Steps to Reproduce

  1. Submit job via API with X-IBM-Notification-URL header specified, pointing to HTTPS server listening for inbound POST sitting behind API ML
  2. Job completes, notification is sent and lost in API ML, app receives nothing

Expected behavior
API ML passes the notification to the app

Logs
Upon request

REST API client (in case of REST API issue):

  • Technology: Node.js
  • OS: Windows 10

Willingness to help
I'm willing.

https://github.com/zowe/api-layer/wiki/Issue-management

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority: HighbugVerified defect in functionalityextenderthis issue has been raised by an extendersize/L

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0