-
Notifications
You must be signed in to change notification settings - Fork 44
Improve API authentication #5163
Copy link
Copy link
Labels
1 - EnhancementImprovements or extensions to existing behaviorImprovements or extensions to existing behavior2 - APIIssues that are related to the APIsIssues that are related to the APIs3 - VerifiedIf an institution makes a request and it has been confirmed to be accurate, this tag will be used.If an institution makes a request and it has been confirmed to be accurate, this tag will be used.
Milestone
Metadata
Metadata
Assignees
Labels
1 - EnhancementImprovements or extensions to existing behaviorImprovements or extensions to existing behavior2 - APIIssues that are related to the APIsIssues that are related to the APIs3 - VerifiedIf an institution makes a request and it has been confirmed to be accurate, this tag will be used.If an institution makes a request and it has been confirmed to be accurate, this tag will be used.
Is your feature request related to a problem? Please describe.
Our current authentication system relies on a CSRF token that is generated when logging in. It is rather cumbersome compared to an approach with an API key and has resulted in many users facing difficulty when trying to make requests via the API.
Describe the solution you'd like
We should add support for an API key/token (or similar approach) that can be generated within the security & accounts system and reused.
Describe alternatives you've considered
You can generate an access token and use it in subsequent requests, but this is more fragile than using an API key.
Reported By
Corinna P at CSIRO on Asana:
Also by Matthew C at UMich: