Ticket #466 (closed requirement: wontfix)

Opened 4 years ago

Last modified 3 years ago

Name of HTTP header for API key shall be configurable

Reported by: johnbywater Owned by: dread
Priority: awaiting triage Milestone: ckan-v1.3
Component: ckan Keywords:
Cc: Repository:
Theme:

Description


Change History

comment:1 Changed 4 years ago by johnbywater

  • businessvalue changed from 100 to 800

comment:2 Changed 4 years ago by johnbywater

  • 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)

comment:3 Changed 4 years ago by johnbywater

  • businessvalue changed from 800 to 500

comment:4 Changed 4 years ago by johnbywater

  • businessvalue changed from 500 to 300

comment:5 Changed 4 years ago by johnbywater

  • 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

comment:6 Changed 4 years ago by dread

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.

comment:7 Changed 4 years ago by dread

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.

comment:8 Changed 3 years ago by thejimmyg

  • 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?

comment:9 Changed 3 years ago by dread

  • Status changed from new to closed
  • Resolution set to wontfix

Agreed

Note: See TracTickets for help on using tickets.