Fix #7944: Adds tls_insecure to the onvif configuration #15603
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
This change adds a new boolean configuration called
tls_insecure
tocameras.*.onvif
allowing the TLS verification to be skipped when connecting to the ONVIF server within the camera device.Some cameras have weird requirements and only expose an HTTPS server using a self-signed certificate for the web service. This change will fix the request on #7944, helping folks with this kind of requirement.
This value will be
False
by default, which means that TLS will be verified, but users can opt to disable this verification by settingtls_insecure: True
.Type of change
Additional information
Checklist
ruff format frigate
)