Request for comment: API keys #251
Closed
codycooperross
announced in
Requests for Comment
Replies: 2 comments 3 replies
|
Thanks for putting this up; I'm a consumer that would love to see this feature implemented. The only additional features I can think of that would be useful is the ability to scope API keys by either read/write access, or by access to specific prefixes e.g. this key can only interact/create/delete DOIs under prefix |
3 replies
|
We recently released the API key feature described above! Learn about DataCite API keys in our latest release notes and explore how to use them with DataCite APIs in our Support documentation. We welcome future API key feedback in the linked release notes post. Thank you to all who contributed their thoughts and suggestions! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
As part of ongoing development in authentication and credentialing, DataCite is planning an implementation of API keys for DataCite APIs, like the REST and MDS APIs, to improve security and usability.
API keys will act as an alternative to sharing repository credentials for API authentication. The current Basic authentication workflow will continue to be supported, and API keys are being designed as a drop-in replacement.
Planned features include:
We welcome community feedback on these improvements to API authentication as we continue development. What features might you need to implement API keys in your DataCite integration? Respond to this post or send us an email at support@datacite.org with your thoughts and suggestions. We will keep this discussion updated as we proceed.
All reactions