Skip to content
This repository has been archived by the owner on Nov 11, 2021. It is now read-only.

Feature Request: Adding the AGENT_SECRET environment variable inside of the config #30

Closed
jacoknapp opened this issue Jan 21, 2020 · 3 comments

Comments

@jacoknapp
Copy link
Contributor

Problem/Motivation

Currently there isn't a good way to add the AGENT_SECRET inside of the portainer config. This Env Var allows you to be able to connect to remote portainer agents on external docker servers, only if the portainer agent also has the same shared secret.

This secret only takes affect when one the agent is restarted, because the agent utilized a trust first connection approach. This is bad if a malicious actor manages to connect to the agent first. To combat this they added the shared AGENT_SECRET env var, which will cause the agent to only pair with the first connection that has the shared secret as well.

As always thank you for all of your great work!

@addons-assistant
Copy link

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

@frenck
Copy link
Member

frenck commented Feb 25, 2020

Merged in dev, will be part of the next release

@frenck frenck closed this as completed Feb 25, 2020
@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Mar 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants