centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 12:58:32 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-74: Corrected order of Edge key components

Browse Source
This commit is contained in:
James Carppe
2023-12-18 01:32:23 +00:00
committed by gitbook-bot
parent 93b3b669cd
commit 1d936b4e12
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
advanced/edge-agent.md
View File

@@ -24,8 +24,8 @@ During the creation process, an Edge ID is dynamically generated. This is a rand
The Edge ID and the join token are unique per environment. The join token (`EDGE_KEY`) is made up of the following base64 encoded data separated by the pipe (`|`) character:
* The Portainer instance API URL. This is how the Edge Agent knows how to ‘call home’ to your Portainer instance.
* The Portainer instance reverse tunnel server address. This is identical to the API URL (unless [changed during deployment](../admin/environments/add/docker/edge.md#deploying) or in [Edge Compute settings](../admin/settings/edge.md#edge-compute-settings)) but with the tunnel server port (`8000` is the default).
* The Portainer instance reverse-tunnel server fingerprint (prevents MITM when creating a tunnel).
* The environment identifier key (endpoint / environment ID).