Layer7 API Management

 View Only
  • 1.  Accept all client certificates of intermediate CA

    Posted Feb 01, 2017 06:46 AM

    We have a client certificate that is signed by an intermediate certificate which is signed by a root certificate. Now we want to build a policy that allows all client certificate that are signed by the intermediate certificate.


    We currently have the following policy

    - Require SSL or TLS Transport with Client Certificate Authentication (So a client certificate has to be present)

    - Authenticate Against Identity Provider


    In the identity provider the intermediate certificate is added as a trusted certificate. This works however it seems that the intermediate certificate is never checked because the authentication works even without having the root certificate installed in the gateway. If we only add the root certificate as a trusted certificate for the identity provider, the authentication fails even if the client sends the whole certificate chain.


    Are there any other ways to accept all client certificates signed by an intermediate certificate, where the whole certificate chain is checked?

  • 2.  Re: Accept all client certificates of intermediate CA
    Best Answer

    Broadcom Employee
    Posted Feb 06, 2017 06:38 PM

    Good evening,


    In the scenario you outlined, it sounds as though the intermediate certificate you have imported has the Trusted Anchor checked on the Validation tab. If you want the entire chain validated you need to import the CA and ensure that the Trusted Anchor is checked and import the Intermediate CA without the Trusted Anchor selected then it will accept all certificates signed by the Intermediate CA and validate up the entire chain. The gateway by default trusts no certificate CA so each level needs to be instructed to be trusted.




    Stephen Hughes

    Director, CA Support

  • 3.  Re: Accept all client certificates of intermediate CA

    Posted Feb 08, 2017 09:11 AM

    Hi Stephan,


    Thank you for your response. During our tests in fact the trust anchor was not checked and that was why we found the behavior and the fact that the gateway accepted the response strange. By closer examining the settings of the gateway we found that our default certificate validation settings were not correct. They were set on "Validate" instead of "Validate Certificate Path". When we changed the setting, we indeed get the behavior you described en the behavior we want.


    Kind regards,

    Leendert Dommicent