CKAN: Ticket #466: Name of HTTP header for API key shall be configurable

businessvalue changed

johnbywater — Fri, 20 Aug 2010 14:06:20 GMT

businessvalue changed from 100 to 800

summary changed

johnbywater — Fri, 20 Aug 2010 17:02:52 GMT

summary changed from Configurable name of HTTP header used for sending CKAN API key (avoid HTTP Auth conflicts) to Name of HTTP header for API key shall be configurable (avoid HTTP Auth conflicts)

businessvalue changed

johnbywater — Fri, 20 Aug 2010 17:20:12 GMT

businessvalue changed from 800 to 500

businessvalue changed

johnbywater — Sat, 21 Aug 2010 21:57:38 GMT

businessvalue changed from 500 to 300

summary changed

johnbywater — Sat, 21 Aug 2010 22:02:12 GMT

summary changed from Name of HTTP header for API key shall be configurable (avoid HTTP Auth conflicts) to Name of HTTP header for API key shall be configurable

dread — Wed, 25 Aug 2010 08:11:06 GMT

As mentioned yesterday, I'm not convinced this is the best way to achieve the actual requirement, which is to access the API securely, and we should discuss this further.

dread — Fri, 27 Aug 2010 15:06:48 GMT

We've agreed that we need another header for this, although it's not clear that it needs to be configurable. We could just accept Authorization OR the new one.

owner, priority set

thejimmyg — Fri, 07 Jan 2011 14:47:13 GMT

owner set to dread
priority set to awaiting triage

What was the original requirement? What's wrong with the current HTTP header name? Can we not mark this as wontfix for now and re-open if needed?

status changed; resolution set

dread — Wed, 12 Jan 2011 12:33:30 GMT

status changed from new to closed
resolution set to wontfix

Agreed