Difference between revisions of "Encryption and GigaFlow Clusters"
From Observer GigaFlow Support | VIAVI Solutions Inc.
(→Overview) |
|||
(2 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Encryption]][[Category:Technical Notes]] | [[Category:Encryption]][[Category:Technical Notes]] | ||
− | |||
== Overview == | == Overview == | ||
− | + | Communication between all clients in a Gigaflow cluster is IP to IP, i.e. unicast. The traffic is routed over https, using [https://observersupport.viavisolutions.com/html_doc/current/index.html#page/oms%2Fcertificate_trust_model.html%23wwweb_certificate_operation TLS based on certificates]. | |
− | Communication between all clients in a Gigaflow cluster is IP to IP, i.e. unicast. The traffic routed over https, using [https://observersupport.viavisolutions.com/html_doc/current/index.html#page/oms%2Fcertificate_trust_model.html%23wwweb_certificate_operation TLS based on certificates]. | + | == Further Reading == |
+ | * See also, [https://observersupport.viavisolutions.com/html_doc/current/index.html#page/oms%2Fcertificate_trust_model.html%23wwweb_certificate_operation Understanding the certificate trust model]. |
Latest revision as of 14:36, 24 September 2019
Overview
Communication between all clients in a Gigaflow cluster is IP to IP, i.e. unicast. The traffic is routed over https, using TLS based on certificates.
Further Reading
- See also, Understanding the certificate trust model.