Skip to content
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.

API authentication tokens and API restrictions #574

Closed
kauffj opened this issue Aug 14, 2018 · 1 comment
Closed

API authentication tokens and API restrictions #574

kauffj opened this issue Aug 14, 2018 · 1 comment
Assignees
@daovist
Labels
needs: exploration Solution unclear, needs research Osprey Spee.ch special project type: new feature New functionality that does not exist yet

Comments

@kauffj
Copy link
Member

kauffj commented Aug 14, 2018

Currently, the spee.ch API is effectively open.

As part of the Osprey project, it will be necessary to restrict API access via an authentication scheme.

Essentially, this means the ability to turn off the API for unauthenticated users and the ability to submit a token with a request that would perform the action as the appropriate authenticated user.
@kauffj kauffj added the Osprey Spee.ch special project label Aug 14, 2018
@alyssaoc alyssaoc added needs: exploration Solution unclear, needs research needs: grooming Issue needs to be groomed before work can start type: new feature New functionality that does not exist yet and removed needs: triage labels Aug 21, 2018
@alyssaoc alyssaoc removed the needs: grooming Issue needs to be groomed before work can start label Oct 4, 2018
@daovist
Copy link
Contributor

daovist commented Oct 12, 2018

this was covered by #605 as well as UI implications of restrictions

@daovist daovist closed this as completed Oct 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@daovist daovist

Labels
needs: exploration Solution unclear, needs research Osprey Spee.ch special project type: new feature New functionality that does not exist yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kauffj @alyssaoc @daovist @lbry-bot