[ckan-dev] CKAN as an API Proxy

Thu Jan 8 21:31:26 UTC 2015

We would like to use CKAN as an API proxy or to find a proxy that would work well with CKAN.

These APIs will be live (“real time”) data feeds and not static datasets.

We have the following desires for such a proxy:
1. We do not want to expose our back-end source APIs to the Internet. All APIs would be requested via the proxy.
2. We would like to take advantage of CKAN's user management/api keys. Ideally each request to the API could be authenticated via CKAN. This may be by using CKAN's api keys or via oauth.
3. We would like a mechanism for managing both the source API URL and the proxy API URL. Ideally there would be one place to create a resource where each URL could be specified.

Attached is an image of a rough diagram of the kind of system we are considering building, but we’re hoping someone has blazed this trail already. Does anyone have any ideas or suggestions for solutions we should explore?

Thank you.

—Andy.
[cid:9FC6C036-9C71-4D19-BAD4-028CFC98A3B4 at nash.tenn]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150108/06c232b6/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CKAN_Proxy.png
Type: image/png
Size: 63004 bytes
Desc: CKAN_Proxy.png
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150108/06c232b6/attachment-0002.png>