iDigi web service issues

I have a ConnectPort X4 uploading data to my idigi.com developer account. I can access the data without any problems through the GUI on the idigi.com website but I am having issues accessing the data through the web service interface. I also have some general questions about the iDigi.com framework.

  1. In the idigi overview document (90001068_A) on pages 17-18, it says that the root collection is always /db and the home collection is always ~. What is the difference between the root collection and home collection?

  2. The authentication is done over regular http (not https). Doesn’t this mean that the authentication data is sent clear text?

  3. When you add a device, you only need to specify the MAC address. While authentication is required to access data files, what is preventing users from adding other users’ devices since all they need to know is the MAC address?

  4. I am having difficulties with accessing a file through the web service using a browser. From the documentation, I am not clear on which URL to use, but with every URL I’ve tried, I always get an error. Depending on the URL, I either get 403 unauthorized or 403 unknown user. If my iDigi connectivity server is sd1-na.idigi.com and my file is at 00000000-00000000-00409DFF-FF3CD525/IOStatus.xml, what URL should I be using?

> I have a ConnectPort X4 uploading data to my
> idigi.com developer account. I can access the data
> without any problems through the GUI on the idigi.com
> website but I am having issues accessing the data
> through the web service interface. I also have some
> general questions about the iDigi.com framework.
>
> 1. In the idigi overview document (90001068_A) on
> pages 17-18, it says that the root collection is
> always /db and the home collection is always ~. What
> is the difference between the root collection and
> home collection?
>

/db represents the root level of the data cache. The home collection, /~, resolves to a particular child collection off the root for the particular user. So, /~ would resolve to something like /db/Red0x/. The home collection is mainly a helper so users do not need to always specify the full path to their main collection.

> 2. The authentication is done over regular http (not
> https). Doesn’t this mean that the authentication
> data is sent clear text?
>

You can also use https. The https port for the sd1-na.idigi.com server is currently configured to 8443. So, a web service call to https://sd1-na.idigi.com:8443/ws/… should work fine.

> 3. When you add a device, you only need to specify
> the MAC address. While authentication is required to
> access data files, what is preventing users from
> adding other users’ devices since all they need to
> know is the MAC address?
>

Only one user at a time can add a particular device. So, if you add one, and then someone attempts to later add the same device, it will fail. Additionally, with the five device limit per user, someone wouldn’t get far trying to randomly guess MAC addresses. In the production pay to use version this would not be as much of an issue due to more information being available about who owns a particular device.

> 4. I am having difficulties with accessing a file
> through the web service using a browser. From the
> documentation, I am not clear on which URL to use,
> but with every URL I’ve tried, I always get an error.
> Depending on the URL, I either get 403 unauthorized
> d or 403 unknown user. If my iDigi connectivity
> server is sd1-na.idigi.com and my file is at
> 00000000-00000000-00409DFF-FF3CD525/IOStatus.xml,
> what URL should I be using?

The following URL (or its https equivalent) should work for accessing that resource:

http://sd1-na.idigi.com/ws/data/~/00000000-00000000-00409DFF-FF3CD525/IOStatus.xml

Chris

Great reply. I tried the link and it worked. I also tried it with port 8443 and https and that worked as well.

The link recently stopped working and starting giving me 403 user unknown errors. I can still log into iDigi.com and I can see that the file is still there. Is this an erroneous error message or is there something wrong with my account?

Hi,

There was a small hiccup with some of the user authentication behind that web service, but it should be working again.

Thanks,
Chris