You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to publish resources with "privileged" data, e.g. user data, possibly donation details etc. To access privileged information we need authentication and authorization. Tastypie provides a basic framework for this that we can use as a starting point.
The text was updated successfully, but these errors were encountered:
Discussions about API keys reached the conclusion that we need API keys both for individual users and for organisations. After some more thought on this I would say API keys bound to organisations is non-trivial at best. The reason for this is that all Django authorization is based on users. There has to be a user account involved whenever we want to access django.auth, i.e. groups and permissions.
Add api resources for Invoice, User and UserProfile models.
Add ApiKey that generates a key associated with a UserProfile when a
profile is saved in the admin
We want to publish resources with "privileged" data, e.g. user data, possibly donation details etc. To access privileged information we need authentication and authorization. Tastypie provides a basic framework for this that we can use as a starting point.
The text was updated successfully, but these errors were encountered: