Robert, is it safe to assume that URL method will be still available till the end of November?

 

Regards,

Grzegorz

 

From: Robert Kisteleki <robert@ripe.net>
Date: Friday, 18 October 2024 at 09:10
To: "Ponikierski, Grzegorz" <gponikie@akamai.com>
Cc: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net>
Subject: Re: [atlas] Changes to RIPE Atlas API keys

 

!-------------------------------------------------------------------|

  This Message Is From an External Sender

  This message came from outside your organization.

|-------------------------------------------------------------------!

 

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:34AM 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