| Re: [volttron-dev] Challenges using the Forward Historian |
|
Ok now to actually answer the question you posed. No the address should just be
192.168.55.55. This will populate the record on the receiver’s auth.json file such as the following: { "domain": null, "address": "127.0.0.1", "mechanism": "CURVE", "credentials": "VqtDy03vqbgRZL8p0UdamVSP4O4OLtis9qAAp6-wbDI", "groups": [], "roles": [], "capabilities": {}, "rpc_method_authorizations": {}, "comments": null, "user_id": "9059a437-e399-4813-990a-36ac953753b9", "identity": "forward_from_first", "enabled": true } In my example I use 127.0.0.1 but that could be any address. Note if you are not seeing ANY connection at all on the receiver then it is likely that your serverkey is not correct in the forwarder config itself.
To get that serverkey, you use the receiver volttron and execute vctl auth serverkey If you have a failure then you know that the server key is correct, but either you have the ip address incorrect or the publickey of the sender volttron isn’t authorized on the receiver. You will see the following error in the receiver’s
logs 2024-10-30 14:51:39,192 () volttron.platform.auth.auth_protocols.auth_zmq [263] INFO: authentication failure: userid='6fcade90-ed17-4c8b-b94e-f18bdff752c8', domain='vip', address='127.0.0.1', mechanism='CURVE', credentials=['VqtDy03vqbgRZL8p0UdamVSP4O4OLtis9qAAp6-wbDI'] Verify that the credentials are the publickey of the forwarder using the sender volttron’s command vctl auth publickey uuid { "destination-vip": "tcp://127.0.0.2:22918", "destination-serverkey": "NNInd2qabB75mW3uweg2NZrXGinqCk3yNRCYN74FAHY" } Successful connection on the receiver should look like the following From: Lazlo Paul <lazlopaul17@xxxxxxxxx> Yes! I am including the credential. I just did not reproduce it here because I did not have a question on it. On Wed, Oct 30, 2024 at 11:36 AM Allwardt, Craig H <Craig.Allwardt@xxxxxxxx> wrote:
|