Layer7 API Management

  • 1.  Custom Private Key: Route https vs Manage HTTP Options

    Posted Feb 07, 2019 06:22 AM

    Is Manage HTTP Options -> SSL/TLS -> Custom Private Key an alternative to setting Custom Private Key on Route HTTPS assertion? Because it looks like it should be (you define client certificate per host) but it does not work for me. Or am I doing something wrong:

     

    1. Route HTTPS -> Select Private Key -> Custom Private Key = OK

    2. Manage HTTP Options -> Add -> TLS/SSL -> Custom Private Key = NOT OK

     

    Kind regards,

    Marcin.



  • 2.  Re: Custom Private Key: Route https vs Manage HTTP Options

    Broadcom Employee
    Posted Feb 07, 2019 06:49 AM

    Hi Marcin,

     

    No, this is not an alternative. The HTTP options do not apply to HTTP routing, only to other HTTP(S) connections.

    See also:

    Manage HTTP Options - CA API Gateway - 9.3 - CA Technologies Documentation 



  • 3.  Re: Custom Private Key: Route https vs Manage HTTP Options

    Posted Feb 07, 2019 07:23 AM

    Thank you very much.

     

    But I'm curious - what is the scenario where HTTP Option configured through Manage HTTP Options would be used? It seems those HTTP options are meant for outbound connections, I don't see any other way of taking advantage of them than through the Route HTTP assertion. Would you be so kind to share some insights into this?



  • 4.  Re: Custom Private Key: Route https vs Manage HTTP Options

    Broadcom Employee
    Posted Feb 07, 2019 07:47 AM

    Hello Marcin,

     

    there are other tasks, that might need a http connection in the background.

    For example the "Access Resource Protected by Oracle Access Manager Assertion" can make use of http connections. Also I believe if you configure the gateway as an http proxy the HTTP options would be used.

     

    Does that help?



  • 5.  Re: Custom Private Key: Route https vs Manage HTTP Options

    Posted Feb 07, 2019 08:50 AM

    Yes, thank you