Skip to content

← All integrations

Firewall and VPN

Renews the J-Web HTTPS certificate over SSH with commit, TLS checks and restoration.

The appliance runs the integration and drives the Juniper SRX / vSRX command line over SSH on port 22. No service agent is installed on the device.

What happens

  1. The appliance connects to the Juniper SRX / vSRX command line over SSH, port 22.
  2. The integration connects over pinned SSH and reuses or loads certificate and key into Junos PKI through SCP. Only the base J-Web HTTPS binding is selected.
  3. The change is checked and committed with a comment, then the binding and TLS leaf are read. If the previous leaf is still served, web-management is restarted once.

Technical details

Connection
The integration runs on the appliance, which connects over SSH, port 22. No service agent is installed.
Service ports
22, 443
What you need
Create a Junos login whose class has view, maintenance, security, configure and system-control, plus reset for the J-Web restart, and may use SCP. Enter its password or unencrypted SSH private key here. Configure J-Web HTTPS under system services web-management https. Read and confirm the SSH host key first.
Platform
SRX/vSRX, Junos 19.1R1+, standalone / MNHA
Actions
Discovery, Installation, Verification, Rollback
Integrations
juniper-srx-ssh 2.0.0
Note
  • A plain commit is used, with no commit confirmed timer. Automatic restoration and rollback use previous_state through SSH and preserve later bindings. A process stop after commit requires separate rollback. Other PKI entries, IKE and SSL proxy are unchanged.

Next steps