Forum Discussion
Hi Gavin,
Yeah, it looks like the "install" part of tmsh isn't plumbed through to the scripting API. That's an oversight and I believe a bug exists for it. However, it might actually be by design since I think you can do what you want to do using "tmsh::create / sys file ssl-cert" and "tmsh::create / sys file ssl-key". I just generated an SSL cert key pair using openssl and successfully imported it using the scripting API.
Here's a code snippet to show what I did:
tmsh::create sys file ssl-cert blah source-path FILE:/var/tmp/blah.crt
tmsh::create sys file ssl-key blah source-path FILE:/var/tmp/blah.key
tmsh::create ltm profile client-ssl blah key blah cert blah
If you needed to generate the key/cert from a tmsh script/iApp, you could do that by using "exec" to invoke openssl - or you can do it off-box and pull the crt/key in using a remote URL in the "file" command. To see help on the file command within tmsh, type "help sys file ssl-cert" or "help sys file ssl-key".
Cheers,
-Brent