Infoblox NIOS Grid Manager
Copy link to the page “Infoblox NIOS Grid Manager”Installs and renews the Grid Manager and WAPI HTTPS certificate on the Grid members you select.
What happens
- The appliance connects to Infoblox NIOS Grid Manager through NIOS WAPI on port 443.
- Discovery finds the WAPI version, Grid members and HA nodes, and the HTTPS certificate subject, SAN, expiry, fingerprint and key type.
- The package checks the certificate and matching key before connecting to Infoblox. It accepts RSA 2048 and RSA 4096 only; ECDSA and other RSA sizes are refused.
- The certificate, CA chain and unencrypted private key are uploaded as one PEM file to each selected member with certificate_usage ADMIN. Management HTTPS restarts immediately and open sessions disconnect. If it fails: Rollback re-uploads the retained previous certificate, chain and key. Discovery cannot retrieve the private key; the package cannot restore the certificate without retained material.
- The package waits for HTTPS and checks the exact SHA-256 fingerprint served by each selected member and its HA nodes. A dropped upload response triggers verification, rather than another upload.
Technical details
- Connection
- The package runs on the appliance, which connects over HTTPS to NIOS WAPI, port 443. No agent is installed.
- Service ports
- 443
- You need
- NIOS WAPI administrator with write permission on each selected member. Superuser is not required.
- Platform
- NIOS 8.6, 9.0 and 9.1
- Actions
- Discovery, Installation, Verification, Rollback
- Packages
-
infoblox-nios-api1.0.0 - Note
-
- Certificates are managed per member, with HA nodes included in discovery and verification. Other Grid members and certificate types are not selected automatically.
- NIOS 9.0.2 and later enforce RFC 5280 on upload. TLS validation is enabled; first contact with a self-signed management certificate requires a saved fingerprint or a trusted CA. Other member and node HTTPS endpoints use their own saved fingerprints through INFOBLOX_MEMBER_TLS_PINS_BASE64 or a trusted CA.
- Rollback requires you to supply previous PEM material through the protected input. Discovery does not retain it automatically. Split large member selections if the combined rollback input exceeds 48,000 decoded bytes.
- The package runs on the appliance or through a service-agent relay, using native Bash and PowerShell 7.4 or later.