This project has moved. For the latest updates, please go here.
SIEGate to SIEGate connections can be made using Transport Layer Security, a highly-secure channel.

In this demonstration setup, we have a SIEGate installation (DEMO01SIEGATE) which is receiving data, and a second SIEGate (DEMO02SIEGATE) which we want to share with. A bidirectional connection will be created, and measurements will be authorised and subscribed.

We'll start with SIEGate on system 2, the system that does not have data. In the menu, click on 'Subscription' -> 'Create Authorization Request'

01.png

There are three sections we need to fill out; Publisher information, Subscriber information, and TLS.

In this case, DEMO01SIEGATE is the publisher. We'll fill in the publisher section as follows:

03-pub.png

This SIEGate, DEMO02SIEGATE, is the subscriber.

03-sub.png

In the TLS section, SIEGate has already filled out the name of the certificate file needed to establish the connection. At this point, we have not yet received this certificate; that will come in later. Right now, we only need to check the 'Self-signed' checkbox. (If you are getting a cert from trusted CA, these steps would be different. This is assuming you're using the default certificates that were generated when you installed SIEGate)

03-tls.png

All together, our settings look like this.

04.png

Once we click create, we're prompted to save our Subscription Request. You'll need to get this file to the publisher in a secure manner; this file will allow them to verify you are you.

After we've saved the request, the device configuration screen is presented.

05.png

Next, we need to switch over to the publisher, DEMO01SIEGATE.

On the publisher, click 'Publication' -> 'Authorize Subscribers'.

10.png

On this screen, we'll click 'Import SRQ' to load the authorization request from the subscriber

11.png

12.png

After we've verified the information is correct, we'll check 'Enabled PG connection'. In this case, we'll also check 'Self-signed'.

13.png

Next, hit 'Save'.

14.png

At this point, the publisher know the subscribers information, and will allow the connection. However, there are no measurements authorized, and there is no connection enable the other direction.

First, we'll create an authorization request from this system (DEMO01SIEGate) to the first one ({DEMO02SIEGate}}). In this connection, the publisher and subscriber roles will be reversed, giving us a true, bidirectional path for data exchange.

01.png

This will be filled out very similarly to the first connection:

15.png

Save the file, and transfer it securely to the other SIEGate.

Now that we have the reverse connection setup, we'll authorise some measurements to be shared. On this system (DEMO01SIEGATE) we have some points available. To authorise the points, click on 'Publication' -> 'Subscriber Measurement Access'.

16.png

By default, no measurements are shared:

17.png

Using the Search box on the right, we'll pick out the Frequency measurement:

18.png

Tick the box next to the measurement, and hit '<<' to move to the authorised list.

19.png

At this point, we have completed everything we need to do on this publisher system. Now, we'll return to DEMO02SIEGATE

On the Browse Devices page, locate the new connection, and ensure 'Enabled' is checked.

21.png

Next, go to 'Subscriber' -> 'Measurement Subscriptions'

22.png

On this page, we'll see the measurement that was made available.

23.png

Tick the checkbox, and move it over to 'Subscribed' with the '<<' button.

24.png

To verify data is flowing, we'll check the graph measurements screen.

25.png

Last edited Oct 3, 2013 at 8:20 PM by arkrohne, version 2

Comments

No comments yet.