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.

Sign up for GitHub

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

Jump to bottom

Status of API keys in CKAN 2.10+ unclear (still supported?) #8195

Open

Chealer opened this issue Apr 23, 2024 · 0 comments

Assignees

Chealer commented Apr 23, 2024

The Authentication and API tokens section of CKAN's API guide contains the following paragraph:

Legacy API keys (UUIDs that look like ec5c0860-9e48-41f3-8850-4a7128b18df8) are still supported, but its use is discouraged as they are not as secure as tokens and are limited to one per user. Support for legacy API keys will be removed in future CKAN versions.

Yet, the Removals and deprecations section of CKAN 2.10's changelog starts with the following item:

Legacy API keys are no longer supported for Authentication and have been removed from the UI. API Tokens should be used instead. See Authentication and API tokens for more details (#6247)

This seems incoherent. I believe the latter is wrong, because it was not updated following CKAN 2.10's release.

wardi self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment