z/OS Connect Enterprise Edition

z/OS Connect

z/OS Connect

Truly RESTful APIs to and from your IBM Z mainframe

 View Only
  • 1.  zOS Connect Defining Filters (Url / IP Address) that can access native server

    Posted 08/14/26 05:15 AM
    Edited by Samantha Catling 08/19/26 10:49 AM

    (May be a re-post .... Sorry     I did not see my first thread) 

    Looking for some guidance on How ? Or is it possible to control where the traffic executing a API Provider defined to our Native zOS Connect Server .

    We are currently running version v3.0.96 (working to rollout v3.0.103/104)

    How can I best define the http Port for our server to only except incoming calls from a controlled list of either IP addresses -or- Url patterns

    For example

    [content removed]

    What is the best way to accomplish this ??
    Is it possible to ensure that ANY traffic coming into our server is coming from our API Catalog (set of Url patterns) and not someone directly connecting to our server address/port?



    ------------------------------
    Scott Adams
    ------------------------------



  • 2.  RE: zOS Connect Defining Filters (Url / IP Address) that can access native server

    Posted 08/14/26 05:19 AM

    Hi Scott, thank you for the question.

    I've spoken to the team and they've explained there isn't a direct way to filter out APIs based on request origin - it's a blanket all or nothing using tcpoptions on the endpoints. You could have individual APIs on different endpoints. I believe the team have spoken to you with more details, but if you haven't already done so, please raise an Idea.



    ------------------------------
    Samantha Catling
    UX & Visual Designer, Z Integration
    IBM
    ------------------------------



  • 3.  RE: zOS Connect Defining Filters (Url / IP Address) that can access native server

    Posted 08/14/26 06:20 AM

    Having different z/OS Connect APIs on different endpoints would not help anything since what you are saying is that there is not direct way to control API usage (in z/OS Connect) based on the request origin.   So, moving the z/OS Connect API to another endpoint (another z/OS Connect server) does not solve the problem, because that server cannot control the Request origin either. 

    Also an IDEA has been opened on August 4th     ZCEE-I-582



    ------------------------------
    Scott Adams
    ------------------------------