API authentication tokens and API restrictions #574

New issue

Closed

opened 2018-08-14 23:00:59 +02:00 by kauffj · 1 comment

kauffj commented

2018-08-14 23:00:59 +02:00

(Migrated from github.com)

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.

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.

daovist commented

2018-10-12 17:11:11 +02:00

(Migrated from github.com)

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

This discussion has been locked. Commenting is limited to contributors.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/spee.ch#574

No description provided.

Rows
Columns