Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (616 - 618 of 2152)

Ticket Resolution Summary Owner Reporter
#349 invalid The system shall support authorised users to edit packages on data.gov.uk johnbywater johnbywater
#354 invalid Collect together requirements and top-level design for user/package 'groups' johnbywater johnbywater

Reported by johnbywater, 4 years ago.

Description

Collect together requirements and top-level design for user/package 'groups': existing tickets, Rufus spec, Sean spec, meeting notes (dread) email, based on existing user authz stuff.

http://knowledgeforge.net/ckan/trac/wiki/AccessControl

Do we add these into user-role table somehow or new table? To present this to team

#357 fixed Fix API documentation, to correct misleading HTTP_AUTHORIZATION statement. johnbywater johnbywater

Reported by johnbywater, 4 years ago.

Description

Sean Burlington wrote:

I recently came across a documentation issue

http://knowledgeforge.net/ckan/doc/ckan/api.html


The key should be passed in the API request header: Header Example value HTTP_AUTHORIZATION fde34a3c-b716-4c39-8dc4-881ba115c6d4


But the header name is actually just 'AUTHORIZATION'

For example to set it in PHP

curl_setopt($ch, CURLOPT_HTTPHEADER, array('AUTHORIZATION: xxxxx-xxxx-xxxx-xxxx-xxxxxxx'));

Note: See TracQuery for help on using queries.