Dear all, An update on this topic: in the past couple of months we reached out to the major users of the old-style API key use. All but one have changed - and I'm chasing the last. Besides these, there are a large amount of small uses of said old style, and we're considering reaching out to them as well via email. That said, I'd like to schedule the decommission of the old use to the end of February. Please keep this in mind if you're affected. Regards, Robert On Fri, Oct 18, 2024 at 9:10 AM Robert Kisteleki <robert@ripe.net> wrote:
Hello,
TL;DR there's still heavy use of the old method, so we need to extend this timeline; I'll put energy into reaching out to identifiable top users.
In the last month the key vs. header use was about 50-50, so clearly we can't remove support for the old method just yet. There are some heavy hitters, so assuming they can make the change there's a chance this can change. It also helps the cause if you can make this change as well :-)
As an explicit call for action for the users reading this: when you use API keys, please use the authorization header ("Authorization: Key xxxxxxx") instead of the query parameter (?key=xxxx).
The other changes were executed as planned.
Regards, Robert
On Fri, Oct 18, 2024 at 1:34 AM Ponikierski, Grzegorz <gponikie@akamai.com> wrote:
Hi!
* We'll deprecate and remove the ability to use the URL form in about a
year (around October 2024).
* We plan to send further reminders about this change over time, as
well
as reaching out to heavy users of the to-be-removed format.
It’s October 2024. Is this plan still valid? I admit that I have a bunch
of tools which use URL form which I would have to update to use "Authorization" header.
Regards,
Grzegorz