![]() Likewise, you tell Octopus the thumbprint of the Tentacle. When Tentacle is configured, you give it the thumbprint (which uniquely identifies the public key) of the Octopus Server. Octopus and Tentacle both have a public/private key pair that they use to establish the TLS connection and verify the identity of the other party. ![]() Regardless of whether Tentacle is in listening mode or polling mode, all communication between the Tentacle and Octopus is performed over a secure ( TLS) connection. We achieve this security using public-key cryptography. Octopus needed to work in scenarios where the Octopus Server is running in your local LAN, close to your developers, while your production servers are running in the cloud or at a remote data center. When designing Octopus, we wanted to make it easy to have secure deployments out of the box, without expecting machines to be on the same domain and without sharing passwords. Others require you to set up usernames and passwords, and to store them in configuration files. Some require machines to be on the same Active Directory domain. ![]() Some deployment technologies are designed for the LAN and have no security at all. This page describes how the Octopus Server and the Tentacle deployment agents communicate in a secure way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |