EPrints Technical Mailing List Archive
Message: #07264
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] ORCID support plugin: refresh token
- To: <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] ORCID support plugin: refresh token
- From: Will Fyson <R.W.Fyson@soton.ac.uk>
- Date: Wed, 11 Apr 2018 10:35:19 +0100
Hi Volker,
At present the the refresh token isn't stored. I'm not entirely sure if it's necessary as part of the EPrints/ORCID integration at the moment, but if we think it would be useful then there may be scope for some further development work on the plugin. Many thanks, Will From: Schallehn, Volker [volker.schallehn@ub.uni-muenchen.de] Sent: 09 April 2018 17:14 To: Eprints-tech Subject: [EP-tech] ORCID support plugin: refresh token Hi all, we have installed the ORCID Support and ORCID Support Advance plugins at a test environment. The review of this installation by the ORCID organisation demands a stored refresh token. But we have only the following tokens stored in the user table: orcid_access_token orcid_granted_permissions orcid_token_expires_year orcid_token_expires_month orcid_token_expires_day orcid_token_expires_hour orcid_token_expires_minute orcid_token_expires_second orcid_read_record orcid_update_works orcid_update_profile Is there any other place where the orcid refresh token could be stored? Thanks in advance. Volker *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/ |
- References:
- [EP-tech] ORCID support plugin: refresh token
- From: "Schallehn, Volker" <volker.schallehn@ub.uni-muenchen.de>
- [EP-tech] ORCID support plugin: refresh token
- Prev by Date: [EP-tech] ORCID support plugin: refresh token
- Next by Date: Re: [EP-tech] ORCID support plugin: refresh token
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):