Template:PCN transition to https

From Teltonika Networks Wiki
Revision as of 15:07, 9 December 2024 by RytisB (talk | contribs) (Created page with "==2024.12.12: Transition to HTTPS protocol RutOS 7.12== With the release of RutOS version 7.12 in January 2025, {{{name}}} devices will disable the HTTP protocol and enable HTTPS Redirect by default to enhance WebUI and API communication security. {| class="wikitable" |- | style="width: 1219px; text-align: left; background: #eeece1;" |PCN Number: PCN_Transition_to_RUTX11_2024.12.12_EN <br> |- |} {| class="wikitable" |+ ! colspan="2" style="text-align: left; background...")

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)

2024.12.12: Transition to HTTPS protocol RutOS 7.12

With the release of RutOS version 7.12 in January 2025, {{{name}}} devices will disable the HTTP protocol and enable HTTPS Redirect by default to enhance WebUI and API communication security.

PCN Number: PCN_Transition_to_RUTX11_2024.12.12_EN
Change description
Change type RutOS Security Enhancement
Detailed description With the release of RutOS version 7.12 firmware, the device's WebUI and API default communication methods will change. The HTTP protocol will be changed to HTTPS (only) in default configuration for security reasons and complying with security standards. The "HTTPS Redirect" functionality will be enabled by default so all HTTP requests will be automatically redirected through the HTTPS channel.
Change reasons To enhance security measures and comply with security standards by eliminating unsecured HTTP protocol usage.
Affected products information
Model Affected order codes Order code changes
RUTX11 All No changes
Upcoming change date January, 2025
Change impact
Risk assessment
  • Users may receive a browser warning indicating that the connection is not secure due to the use of a self-signed certificate in HTTPS.
  • API users may experience issues depending on the tools they use to communicate with the API, as some may not support HTTPS, self-signed certificates or the tooling may have to be reconfigured to adapt to these changes.
Suggested implementation plan
  • Information included in this PCN will help adapt to the upcoming changes. For more detailed information, please contact your sales representative. Use the following guidance on how to proceed when encountering browser warnings due to self-signed certificates.
  • API users should update their tools and scripts to support HTTPS communication and handle self-signed certificates.
Acknowledgement of PCN receipt
If no feedback is received within two weeks after the issue date of this notification, Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above.

To download the PDF version of this notification, click here.