Forum Discussion
Grant_Joy_24163
Oct 06, 2016Altostratus
The requested ClientSSL Profile (/Common/url.com) already exists in partition Common.
I am getting this error when I push a cert. What is the best way to handle this case? It happens when I use POST. I tried PUT and PATCH and they don't work. Should I DELETE this and then POST it?
T...
- Oct 12, 2016
I solved this issue by using a combination of POST and PUT.
The initial POST is needed if it is a new profile. I attempt a PUT to
. If I get an unsuccessful response on this, I attempt a POST to/mgmt/tm/ltm/profile/clientSsl/$DOMAIN
with a body that looks like/mgmt/tm/ltm/profile/clientSsl
which means it has created the profile for the first name.{ 'name' => "$DOMAIN", 'cert' => "$DOMAIN.crt", 'key' => "$DOMAIN.key" }
This seems to handle renewals as well as first time creations.
Grant_Joy_24163
Oct 12, 2016Altostratus
I solved this issue by using a combination of POST and PUT.
The initial POST is needed if it is a new profile. I attempt a PUT to
/mgmt/tm/ltm/profile/clientSsl/$DOMAIN
. If I get an unsuccessful response on this, I attempt a POST to /mgmt/tm/ltm/profile/clientSsl
with a body that looks like { 'name' => "$DOMAIN", 'cert' => "$DOMAIN.crt", 'key' => "$DOMAIN.key" }
which means it has created the profile for the first name.
This seems to handle renewals as well as first time creations.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects