Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Journal submission system integration #160

Open
acabunoc opened this issue Mar 1, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@acabunoc
Copy link
Member

commented Mar 1, 2016

Update our API to make it easy for journals/publishers to integrate their submission systems with Paper Badger. Currently, publishers fill out a form listing all authors.

  • Add authentication on our API
  • create endpoints for adding a paper

@acabunoc acabunoc referenced this issue Mar 1, 2016

Open

Roadmap #17

@jinankjain

This comment has been minimized.

Copy link
Contributor

commented Mar 13, 2016

Hey @acabunoc Could you please elaborate on this? Like currently our api already required authentication like for issue and adding a paper we need auth for that.

What sort of endpoints we want to create for adding a paper?

@acabunoc

This comment has been minimized.

Copy link
Member Author

commented Mar 15, 2016

Thanks @jinankjain for the questions, I hope this clarifies things!

We need to add authentication so publishers can securely consume parts of the api (like adding a new paper via POST request instead of a form). The same way we use the ORCID api by providing a key, publishers would do something similar with our app to issues badges on their papers.

@jinankjain

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2016

It is sort of we have implement our Oauth2.0 according to RFC

@acabunoc

This comment has been minimized.

Copy link
Member Author

commented Mar 16, 2016

well, I assume a library has implemented this and we can use it, but yes I think so

@jinankjain

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2016

Ok, I will look into libraries.

@jinankjain

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2016

@amitkumarj441

This comment has been minimized.

Copy link

commented Jun 17, 2016

Hi @acabunoc ,

Actually, the authorization is processed using multiple predefined URLs, and hence endpoints
But Here, we've have 3 endpoints:

  1. Request URL (this endpoint passes the request token)
  2. Access URL (exchanges request token for an access token)
  3. Authorize URL (confirms that the access token is valid)

Do we need to create all these endpoints?

Cheers,
Amit Kumar Jaiswal

@josmas

This comment has been minimized.

Copy link
Member

commented Oct 20, 2016

Bit of research on this issue: We've looked at Stormpath to be able to get this up and running quickly. It's free for up to 10K calls/month, which would be enough for now.

They have an express library, but after a quick experiment, our React front-end is getting in the way of the routes that Stormpath needs to add. They also have a React SDK that uses React Router, but our router is too out of date, so this will need a bit of work. May be a good idea to take care of #201 before attempting this again.

@acabunoc

This comment has been minimized.

Copy link
Member Author

commented Oct 20, 2016

Stormpath seems like a good solution if we can get it working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.