Closed achingbrain closed 9 years ago
Right now, any client can connect to pm2-interface, invoke RPCs and receive events.
Some sort of authentication mechanism is necessary in order to prevent rogue clients wreaking havoc on production systems.
Either public keys, passwords over SSL, encrypted tokens or similar would do the trick.
Or should this go into axon/axon-rpc instead?
https://github.com/Unitech/pm2/issues/260
Doesn't look like axon will support authentication without some work - https://github.com/visionmedia/axon/issues/107
Right now, any client can connect to pm2-interface, invoke RPCs and receive events.
Some sort of authentication mechanism is necessary in order to prevent rogue clients wreaking havoc on production systems.
Either public keys, passwords over SSL, encrypted tokens or similar would do the trick.
Or should this go into axon/axon-rpc instead?