Reference16r1:Concept App Service Connector for Let's Encrypt
The Connector for Let's Encrypt App is an app which handles certificate creation for innovaphone gateways and App Platforms.
Applies To
- innovaphone firmware and apps V14
Requirements
- innovaphone gateways
- innovaphone Application Platform (image version 110036 or higher)
- Firmware V14 or higher
- Certificates for IP addresses: Let's Encrypt App, firmware and App Platform Manager V16r1 SR8 or higher
Concept
The innovaphone Service Connector for Let's Encrypt App handles the communication between innovaphone gateways or the App Platform Manager and the Let's Encrypt API based on the protocol ACMEv2.
How it works
Certificates for IP addresses
Besides DNS names, innovaphone gateways and the App Platform Manager can request certificates for IP addresses. Let's Encrypt issues such certificates only with its shortlived profile:
- The certificate is currently valid for 160 hours (about 6.7 days) and has no common name (CN); all names are subject alternative names. A certificate with DNS names and IP addresses is short-lived as well.
- The IP address must be public and reachable by Let's Encrypt on TCP port 80 (http-01 challenge). Let's Encrypt rejects private and other reserved addresses; the error is shown in the log of the Let's Encrypt settings.
- The option Use as CN cannot be used together with an IP address.
- A device with an IP address configured that is connected to an older Let's Encrypt App without support for IP addresses raises an alarm and retries slowly.
Renewal and installation depend on the validity of the current certificate:
| Certificate valid 10 days or more | Certificate valid less than 10 days (short-lived) | |
|---|---|---|
| New certificate is requested | when a third of the validity is left (30 days for a certificate valid 90 days) | when half of the validity is left (80 hours for a certificate valid 160 hours) |
| New certificate is installed | Certificate installation before expiry (days) before expiry, default 3 days | Installation of short-lived certificates before expiry (hours) before expiry, default 48 hours |
A certificate installed by a version before V16r1 SR8 is renewed 30 days before expiry, as before.
Let's Encrypt issues at most 5 certificates for the same set of names within 7 days. The regular renewal of a short-lived certificate needs about 2 per week.
Apps
There is no App provided by this App Service.
PBX Manager Plugins
Let's Encrypt Config
This PBX Manager Plugin allows the configuration of the Let's Encrypt URL itself and further settings, see Apps/PbxManager/App Connector for Let's Encrypt.
Configuration
Troubleshooting
Trace flags for App on App Platform:
- App
- Database
- App Websocket
- HttpClient
Requests the App refuses (e.g. App not enabled, subscriber agreement not accepted, invalid IP address) are shown in the log of the Let's Encrypt settings together with the device and the requested names.
Known issues
- Certificates for IP addresses have no common name. Functions that identify a certificate by its common name only (e.g. certificate based registrations or the certificate lists of the device admin UI, which show <No name>) cannot use them.
- With the default installation offset of 48 hours, a gateway may show the alarm "A certificate has expired or will expire soon" for about 5 hours before the new short-lived certificate is installed.