Forum Discussion

Dan_L1's avatar
Dan_L1
Icon for Nimbostratus rankNimbostratus
Nov 11, 2015

LTM v12.0.0 - Rest API, client-ssl no longer supports PUT

Is there a reason the REST API for version 12.0.0 no longer allows PUT for client-ssl?

According to the documentation:

REST Endpoints
Collection URI
/mgmt/tm/ltm/clientssl
Collection Methods
OPTIONS, GET
Resource URI
/mgmt/tm/ltm/clientssl/~[resource id]
Resource Methods
OPTIONS, GET
Resource Natural Key

We utilized the PUT feature here to assist with certificate automation, we're currently running 11.5.1 HF10 and it works fine (ran fine on 11.6 as well). We're in the process of working with 12.0.0 prepping for next years upgrades and noticed it's no longer supported. Is there a reason/can it be re-added?

3 Replies

  • Have you confirmed it no longer works? I see that entry in the Reference guide which is brand new for v12, but I can't image the ability to add or update a client-ssl profile would have been removed if it existed previously. The schema in the reference guide could just be wrong. Can you test any where? I can test this tomorrow in my lab if you don't have a test box.

     

  • Dan_L1's avatar
    Dan_L1
    Icon for Nimbostratus rankNimbostratus

    Yeah, just inspected further and looks like I was looking at the wrong client-ssl field in the documentation. This can be ignored (it's actually under mgmt/tm/ltm/profile/clientSsl & mgmt/tm/ltm/profile/clientSsl/certKeyChain