Project

General

Profile

Actions
Copy link

Feature #1233

open

API: External Authentication

Added by Bernhard Koschiček-Krombholz over 4 years ago. Updated about 2 years ago.

Status:
Acknowledged
Priority:
Normal
Assignee:
-
Category:
API
Target version:
Wishlist
Start date:
2020-05-10
Estimated time:

Description

External Authentication will be needed for projects who want a frontend without exposing all data (no public API).
For implementing an API authentication method see: Whitepaper, authentication-with-flask

To consider: webclients will request data so we can't e.g. just block IPs or similar.

Related issues 1 (0 open — 1 closed)

Related to OpenAtlas - Feature #1377: API: IP restrictionsClosedAlexander Watzinger2020-10-03Actions
Actions
Copy link
 #1

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Status changed from New to Assigned
Actions
Copy link
 #3

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Target version set to 208
Actions
Copy link
 #4

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Subject changed from External Athentification to External Authentification
  • Status changed from Assigned to Acknowledged

For the moment postponed!

Actions
Copy link
 #6

Updated by Alexander Watzinger over 4 years ago

  • Status changed from Acknowledged to Assigned
Actions
Copy link
 #7

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Target version changed from 208 to Wishlist
Actions
Copy link
 #8

Updated by Alexander Watzinger about 4 years ago

  • Subject changed from External Authentification to API: External Authentification
  • Status changed from Assigned to Acknowledged
  • Assignee deleted (Bernhard Koschiček-Krombholz)
Actions
Copy link
 #9

Updated by Christoph Hoffmann about 4 years ago

  • Subject changed from API: External Authentification to API: External Authentication
Actions
Copy link
 #10

Updated by Alexander Watzinger about 4 years ago

  • Description updated (diff)
Actions
Copy link
 #11

Updated by Bernhard Koschiček-Krombholz about 4 years ago

  • Assignee set to Bernhard Koschiček-Krombholz
Actions
Copy link
 #12

Updated by Alexander Watzinger about 4 years ago

  • Description updated (diff)
  • Status changed from Acknowledged to Assigned
  • Target version changed from Wishlist to 208

Moving this from wishlist again because we'll need it for projects who want a frontend without exposing all data.

Actions
Copy link
 #13

Updated by Alexander Watzinger about 4 years ago

I was thinking about the authentication issue. The API is either accessible (public) or not and authentication via frontend gets tricky because requests are sent from some web client.

We will have to solve this at some point but we can deal with it for now:
  • For testing we can use the Origins project, it has a small data set (so less likely performance issues) and the API is already set public.
  • For concluded projects it shouldn't be a big issue, e.g. the demo versions MEDCON and DPP are already cleaned up data wise and open anyway (nevertheless we will ask for permission).
  • THANADOS is a case where we have a public frontend but not all data should be accessible BUT because the THANADOS frontend uses Flask we could implement an IP restriction (#1377)
Actions
Copy link
 #14

Updated by Bernhard Koschiček-Krombholz almost 4 years ago

Actions
Copy link
 #15

Updated by Alexander Watzinger about 2 years ago

  • Status changed from Assigned to Acknowledged
  • Assignee deleted (Bernhard Koschiček-Krombholz)
  • Target version changed from 208 to Wishlist
Actions
Copy link

Also available in: Atom PDF