Template:PCN transition to https: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
 
Line 1: Line 1:
==2024.12.12: Transition to HTTPS protocol RutOS {{{RutOS}}}==
=={{{date}}}: Transition to HTTPS protocol RutOS {{{RutOS}}}==


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

Latest revision as of 15:47, 9 December 2024

{{{date}}}: Transition to HTTPS protocol RutOS {{{RutOS}}}

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

PCN Number: {{{PCN_number}}}
Change description
Change type RutOS Security Enhancement
Detailed description With the release of RutOS version {{{RutOS}}} 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
{{{name}}} {{{code_name}}} {{{order_code}}} {{{order_code_changes_data}}}
Upcoming change date {{{quarter}}}
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.
  • 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, [[Media:{{{PCN_number}}}_EN.pdf|click here]].