Im setting up my first Agent, but when I download the Agent Manager and follow the guide from Add agent | Flow Connect Help , I end up being prompted this:
The problem is that this is my first agent, and I have not yet received an appSettings.installer.json. My intuition tells me that this is generated with the first agent, but I don’t know. I even tried creating my own appSettings.installer.json and was hoping it would write to that, but that gave me no luck.
You are exactly right, it indicates that there is another agent already set up prior to this. If you check in the hub - admin - agents, are you sure you do not already have a group there?
What that file contains is the encryption key; since you, as the customer, own it, it is, by design, nothing we have any control over at Novacura. For good and bad of course.
There are other groups with existing agents. However I’d expect to be able to create a brand new one by creating a new group assigning new agents to it. Im working in a domain where people are working on different projects with agents for different purposes. I guess it would be very inconvenient if we have to pass around the json file for every new user coming into the domain.
The agent here is to connect to your ERP or another system. Just want to make sure the word ‘Agent’ isn’t misleading. Can you give me an example of what you are looking to achieve, please?
Im building an external system we want to run locally on our network. However to make the communication between this local service and Novacura Cloud seemless an agent would solve that perfectly sending data through amqp.
Ok, that is what the agent is doing. So yes, the encryption key for your Connect organization is created when the first agent is set up, and that is the one that must be used going forward, as you have concluded. Sorry for the inconvenience.
I managed to get the old appSettings.Installer.json previous created on another machine. Im up and running with the agent now However it would be convenient if the installer had a better way of validating/retreiving the keys instead of having to send them between operators. Thanks for your help!
However it would be convenient if the installer had a better way of validating/retreiving the keys instead of having to send them between operators. Thanks for your help!