Certificate Provisioning to F5 BIG-IP
Certificate Provisioning to F5 BIG-IP lets you push a certificate stored in Akeyless directly to an F5 BIG-IP device, using an existing F5 Target. This is one of the certificate provisioning destinations supported by Akeyless.
Provisioning uploads the certificate, the private key, and optionally the chain to the F5 as traffic certificate and key objects. You can also bind the certificate to existing SSL profiles.
Not Supported for F5 BIG-IPThe
post-provision-commandparameter and the PFX certificate format aren't supported for F5 BIG-IP. Certificates are always uploaded as traffic certificates.
Provisioning a Certificate Using the Akeyless CLI
akeyless assoc-target-item \
--name <Certificate name> \
--target-name <F5 Target name> \
--gateway-url 'https://<Your-Akeyless-GW-URL>:8000' \
--certificate-path </Common/my-cert> \
--private-key-path </Common/my-key> \
--chain-path </Common/my-chain> \
--bind-ssl-profiles client-ssl:Common:my-profile \
--f5-save-config \
--f5-sync-device-group <Device group name>Where:
certificate-path: Required. The certificate object, in the format/<partition>/<name>, for example/Common/my-cert. Nested sub-paths aren't supported for file objects.private-key-path: Optional, the private key object, in the same format. If not set, the key uses the certificate's path.chain-path: Optional, the chain object, in the same format.bind-ssl-profiles: Optional, binds the certificate to an existing SSL profile, in the format<type>:<partition>:<name>, where<type>isclient-sslorserver-ssl. Leave the partition empty to use the certificate's partition, or add a folder for a profile under an application folder, for exampleclient-ssl:Common/Shared:my-profile. To bind several profiles, repeat the flag. Binding requires both the certificate and the private key. Without this flag, only the certificate and key objects are uploaded, and no SSL profile is changed.f5-save-config: Optional, saves the F5 running configuration after each successful provisioning, so the certificate survives a reboot. This also saves any other unsaved change on the device.f5-sync-device-group: Optional, syncs the configuration to this device group after each successful provisioning, so the HA peer serves the same certificate. This impliesf5-save-config, and it overwrites unsynced changes on the other members of the group. If the device group doesn't exist, provisioning fails before anything is uploaded.
You can find the complete list of parameters for assoc-target-item in the CLI Reference - Encryption Keys section.
Provisioning a Certificate Using the Akeyless Console
- Log in to the Akeyless Console, go to Items, and find the certificate you wish to provision.
- Click on the Certificate item, and click on the Provisioning tab.
- Click Attach to add a new row to the table.
- Enter the following parameters:
- Target Name - Choose an existing F5 Target from the drop-down list.
- Gateway - Choose the Gateway that provisions the certificate.
- Certificate Remote Path - The certificate object, in the
/<partition>/<name>format. - Private Key Remote Path - The private key object, in the same format.
- Certificate Chain Path - The chain object, in the same format.
- Bind to SSL Profile(s) - If set, the certificate is bound to an existing SSL profile.
- Profile Type - Select Client SSL or Server SSL.
- Partition - The partition where the profile exists. By default, the partition is taken from the Certificate Remote Path.
- Profile Name - The name of the SSL profile.
- Click Save. The target is added as a new row in the Provisioning table.
Updated about 1 hour ago
Did this page help you?
Suggest Edit
