[atlas] API Keys problem?
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] Result streaming lacking results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Fri Mar 9 09:49:30 CET 2018
Hi, There was a bug allowing to get non-public built-in results from non-public probes. Therefore probes must be added to the key you want to get access to. Now it is fixed and lead to adding probes to 'probes - Get non-public measurement results' API key. Sorry for the hassle. wbr /vty On 3/8/18 6:40 PM, Ponikierski, Grzegorz wrote: > > Glad to hear that :) > > It was strange to me because I already had 'measurements - Get results > from a non-public measurements' which worked fine. So now I have: > > 'measurements - Get results from a non-public measurements' > > 'probes - Get non-public measurement results' > > It looks quite redundant for me but it works :) > > Regards, > > Grzegorz > > *From: *Daniel Ankers <md1clv at md1clv.com> > *Date: *Thursday 2018-03-08 at 18:36 > *To: *"Ponikierski, Grzegorz" <gponikie at akamai.com> > *Cc: *"ripe-atlas at ripe.net" <ripe-atlas at ripe.net> > *Subject: *Re: [atlas] API Keys problem? > > Hi Grzegorz, > > "probes - Get non-public measurement results" is exactly what was > needed - thank you! > > Regards, > > Dan > > On 8 March 2018 at 17:30, Ponikierski, Grzegorz > <gponikie at akamai.com<mailto:gponikie at akamai.com>> wrote: > > Hi! > > I had the same issue 28^th Feb. I had to add 'probes - Get > non-public measurement results' to my API key to fix it. > > Regards, > > Grzegorz > > *From: *Daniel Ankers <md1clv at md1clv.com<mailto:md1clv at md1clv.com>> > *Date: *Thursday 2018-03-08 at 18:27 > *To: *"ripe-atlas at ripe.net<mailto:ripe-atlas at ripe.net>" > <ripe-atlas at ripe.net<mailto:ripe-atlas at ripe.net>> > *Subject: *[atlas] API Keys problem? > > Hi, > > Has there been a change in the way that API keys work for the > measurement results API? > > I've got an API key which is granted permission to get results > from a non-public measurement. When I do: > > curl -H "Authorization: Key $KEY" > "https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlas.ripe.net_api_v2_measurements_-24MEASUREMENT_results_-3Fstart-3D&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XA7UqyUiWhQ8cJzGZlnLA89Ync-_75lLOvUCSOji-4w&m=iNz0AYGxeocaIuxLsWKwKh7K2h16JzQdTtmW8FDBRM8&s=03N6T0foyEskCISQ98sngVX9ouV1p9LqRtRch3UuQvM&e=>1520510400" > > (Replacing $KEY with the key and $MEASUREMENT with the measurement > ID) I get: > > {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your > keys has no grants"}],"code":102,"detail":"There was a problem > with your request","title":"Bad Request"}} > > This was previously working, but I'm not sure exactly when it > stopped. I've checked that getting the data through my browser > works while I'm logged into the site, and that if I request > https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlas.ripe.net_api_v2_measurements_-24MEASUREMENT_latest&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XA7UqyUiWhQ8cJzGZlnLA89Ync-_75lLOvUCSOji-4w&m=iNz0AYGxeocaIuxLsWKwKh7K2h16JzQdTtmW8FDBRM8&s=_Dap2R7tBQ2vl_PClpD1bzGT6Hu_4P0mfvEqEyKxvPs&e=>using > the API key I get data returned. > > Regards, > > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20180309/060dd9b9/attachment.html>
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] Result streaming lacking results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]