At least three organizations encountered an unexpected URL must include protocol (http:// or https://) or be a SSH URI exception when attempting to modify a root. The issue started on UTC-5 23-08-16 19:14 and was reactively discovered 14.8 hours (TTD) later by a user who reported [1] that he encountered the exception while trying to modify a field in an existing root. The problem was resolved in 5.7 hours (TTF) resulting in a total impact of 20.6 hours (TTR).
The problem was caused by a regex error in the utility responsible for validating the format of the root URL [2]. The regex did not correctly validate the URLs, leading to the exception being thrown.
The regex responsible for validating the roots URL was corrected [3].
Validation was not tested with all possible URL formats for roots. MISSING_TEST