F5 Connector
This section details how to configure the F5 Connector.
Prerequisites
On the F5 BigIP side, you need to create a technical user for Horizon, with one of the following roles:
-
Administrator, which applies to local and remote accounts. -
Resource Administrator, for a local account. On the F5 BigIP, this role always applies to all partitions. Through iControl REST, the F5 BigIP lets onlyAdministratoraccounts upload files, so the account also needs an iControl REST role that allows the certificate upload, and the connector F5 Login Provider is set totmos.
The iControl REST role is created with an Administrator account:
curl -sk -u <admin login> -H "Content-Type: application/json" \
-X POST "https://<F5 BigIP hostname>/mgmt/shared/authz/roles" \
-d '{"name":"horizon-upload",
"userReferences":[{"link":"https://localhost/mgmt/shared/authz/users/<technical user>"}],
"resources":[{"restMethod":"POST","resourceMask":"/mgmt/shared/file-transfer/uploads/*"}]}'
After performing these steps, you will get the following information, required later:
-
the technical user login/username
-
the technical user password
How to configure F5 Connector
1. Log in to Horizon Administration Interface.
2. Access F5 Connectors from the drawer or card: .
3. Click on .
4. Fill the mandatory fields.
General
-
Name* (string input):
Enter a meaningful connector name. It must be unique for each connector. Horizon uses the name to identify the connector. -
F5 BigIP hostname* (string input):
Enter the F5 BigIP management interface hostname (DNS or IP address), followed by the port when it is not443(for examplebigip.example.com:8443). -
F5 BigIP credentials* (select):
SelectLogincredentials containing the username and password created for Horizon in the F5 BigIP, with one of the roles described in the prerequisites. -
F5 Login Provider (string input):
Login provider to use in TACACS authentication mode.tmosfor example. Set it totmosfor a localResource Administratoraccount. -
Proxy (string select):
The HTTP/HTTPS proxy to use. -
Timeout (finite duration):
Set by default at 10 seconds. Must be a valid finite duration. -
Max stored certificates per holder* (int):
Maximum number of certificate and key pairs kept on the F5 BigIP for each holder (client SSL profile). At each renewal, Horizon removes the oldest pairs beyond this number. Must be greater than 0. -
TLS Insecure (boolean):
If enabled, TLS validation will ignore expired, invalid or untrusted certificates.
| This is not recommended for production usage |
Assets identification
-
Partition (string input):
F5 BigIP partition to manage.Commonby default. -
SSL parent (string input):
Name of the parent Client SSL Profile, located in the managed partition.clientsslby default. -
Prefix (string input):
Prefix of the names given to the client SSL profiles, certificates and keys created by Horizon.hrz-by default. -
Cipher group (string input):
Name of the Cipher group, located in the managed partition.Noneby default. -
Version (string input):
Major version of the F5 BigIp instance. For a F5 instance in15.1.10use15.0.0for example.13.0.0by default. -
Override profile configuration (boolean):
If enabled, the SSL Parent and the Cipher Group will be overridden when updating a client profile.trueby default.
-
Persist configuration (boolean):
If enabled, Horizon saves the F5 BigIP configuration tobigip.confafter each successful deployment, so that pushed certificates are not lost if the appliance restarts before its scheduled configuration save. If the save fails, the deployment is reported as failed.falseby default.
| The save covers the whole running configuration of the F5 BigIP, including changes made by other administrators and not saved yet. |
The CA chain objects pushed to the F5 BigIP are named after the Prefix, followed by the name of the issuing CA when the F5 object name length allows it, and end with <chain hash>-CHAIN.crt. CA chains pushed by earlier versions under the hash-only name are left in place, and the client SSL profiles managed by Horizon are bound to the renamed chain on their next push.
|
Actors and renewal management
These configuration elements mainly define the number of authorized interactions with the remote service on a defined period. For example, one needs to ensure that the remote service will not be contacted more than 5 times per 3 seconds. Throttle parallelism defines the number of times and Throttle duration the period of time. Therefore, on the above example, throttle parallelism would be set to 5 and throttle duration would be set to 3 seconds.
-
Throttle duration* (finite duration):
Set by default at 3 seconds. Must be a valid finite duration. -
Throttle parallelism* (int):
Set by default at 3.
5. Click on the save button.
You can update or delete
the F5 Connector.
|
You will not be able to delete an F5 Connector if it is referenced in any other configuration element. |
Synchronize your third party
Your third-party certificates can be synchronized with Horizon using scheduled tasks.
Scheduled tasks are a functionality of WebRA that allows to synchronize automatic renewal or revocation events with a third party periodically with what occurs on a WebRA profile. To be more specific, it will periodically check whether the certificate has entered the "renewal period" that was defined in the connector’s configuration, and renew it automatically if necessary.
1. Refer to the third party connector documentation to create a third party connector.
2. Ensure you have an existing WebRA Profile: renewal will be automated on the selected profile.
3. Follow the documentation of the WebRA Scheduled Tasks section to properly configure a scheduled task.