karthik / karthik/zenodo

authentication via OAuth2.0?

Open
#2 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
R
Stars
18
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Took a quick look at doing the authentication via OAuth2.0 instead of a personal token (Means a user can just click "authorize app" in the browser instead of having to create and store a private token and then manually load that into R). Unfortunately I've run into trouble; cannot tell how much of this is due to how httr is making the authentication request (https://github.com/hadley/httr/issues/167) or issues on Zenodo's end, but I've contacted both. Just putting this here as a placeholder meanwhile.

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files or tests are named. Start by reviewing the linked httr issue 167 and the existing authentication flow in the repository, then compare it with Zenodo's OAuth behavior. Done means browser authorization works without requiring users to create, store, and manually load a personal token into R.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
authentication
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.