search

IATI / ckanext-iati

CKAN extension for the IATI Registry
http://iatiregistry.org
9 stars 6 forks source link

How can someone delete their legacy API Keys? #450

Closed robredpath closed 2 months ago

robredpath commented 6 months ago

I understand that, when we upgrade to 2.10, legacy API keys will stop working.

As part of the preparation for this, I want to write some documentation to help users migrate.

If I were making such a migration myself, I would want to be able to delete my legacy API keys after setting up with tokens, so that I could reassure myself that my systems still worked once API Keys are gone, and that there wasn't some failure forthcoming.

As I understand it, @cormachallinanderilinx , there is no UI in 2.9 to delete legacy API Keys.

Please can you confirm if this is the case, and if so, if there is any method available to us to disable keys? Can we, for example, remove them via the API? I had a look at the API reference but nothing in ckan.logic.action.delete looked relevant.

robredpath commented 6 months ago

@cormachallinanderilinx this PR is what confuses me - that suggests that the UI for dealing with API keys was present in early 2.10 releases (and therefore would also be in 2.9) but we can't seem to see it.

robredpath commented 4 months ago

As an alternative, @cormachallinanderilinx has suggested that once individual users have confirmed that they have migrated, we can check in the new logging to make sure that they have, in fact, stopped using keys.

robredpath commented 2 months ago

We've ascertained that this isn't possible.