Forum Discussion
Separate Key and Certificate vs RSA Certificate & Key
- Mar 01, 2016
There's no big difference, only the number of configuration objects varies. If you do the second option, the certificate you import will be automatically named the same as your key object. Since name overlaps, a merged object will be created. I prefer to keep a matching certificate and private key in one configuration object (RSA Certificate & Key).
You can achieve the same merged object solution if you import certificate and key separately, but with the exact same object name. If there's any difference in naming, you will end up with two objects instead.
There's no big difference, only the number of configuration objects varies. If you do the second option, the certificate you import will be automatically named the same as your key object. Since name overlaps, a merged object will be created. I prefer to keep a matching certificate and private key in one configuration object (RSA Certificate & Key).
You can achieve the same merged object solution if you import certificate and key separately, but with the exact same object name. If there's any difference in naming, you will end up with two objects instead.
- dragonflymrMar 01, 2016CirrostratusHi, Thanks for info. So if I have just one RSA Certificate & Key object should I choose it for both Key and Certificate fields when for example setting clientssl profile - so same file chosen for Certificate and Key? Piotr
- Hannes_RappMar 01, 2016Nimbostratusthat's right
- dragonflymrMar 01, 2016CirrostratusThanks
Recent Discussions
Related Content
* 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