search

gbif / content-crawler

Crawls CMS and articles from Mendeley into ElasticSearch indexes
Apache License 2.0
1 stars 1 forks source link

New Mendeley auth flow #19

Closed dnoesgaard closed 5 years ago

dnoesgaard commented 5 years ago

Email from Mendeley pasted below:

We want to always provide the best support to users and developers using Mendeley APIs, and so we have recently changed the authentication flow. Mendeley is now fully integrated with the Elsevier authentication mechanism.Using this new flow for your client authorization requests will give your users an improved user journey. For example, they will be able to register for a new Mendeley account as part of the authorization flow, or even choose to authenticate with their institution, organization or Athens account instead of their Elsevier username and password. Please see more information here.All apps need to be updated to the new authorization flow by 1 November 2019. Please follow the steps below to update your apps.Sign in to dev.mendeley.com with your Mendeley credentials. Your user name is comms@gbif.org. If you have forgotten your password you can reset it here;In My Apps, please select each application using the Mendeley APIs;You will find two options for the authorization flow, ‘legacy’ and ‘Elsevier’ (recommended);In the case of the application being set as ‘legacy’ please change it to ‘Elsevier’ and click update.

If you would prefer to re-register your apps and include the new secret key, you can follow these steps:Sign in to dev.mendeley.com with your Mendeley credentials. Your user name is comms@gbif.org. If you have forgotten your password you can reset it here;In My Apps, please re-register all the applications using the Mendeley APIs;Please select the new authorization flow, ‘Elsevier’ (recommended);Accept the Terms and Conditions and generate a new secret key – one per application;Implement the new secret key in your application code. Please note that apps using the ‘legacy’ authorization flow will not work from 1 November 2019.

I don't know if this affects the way we crawl Mendeley?

dnoesgaard commented 5 years ago

Simply changing the auth workflow on the api app (id: 5514) appears to have been enough. Closing this for now...