This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] API Keys problem?
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] API Keys problem?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcel Flores
marcel.flores at verizondigitalmedia.com
Thu Mar 8 18:33:55 CET 2018
We had a similar issue on 28th Feb -- though I think our error was that there were no grants on the key (it had been working for months, showed fine on the UI). I just made a new key and had no issue after. -m On Thu, Mar 8, 2018 at 9:30 AM, Ponikierski, Grzegorz <gponikie at akamai.com> wrote: > Hi! > > > > I had the same issue 28th 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> > *Date: *Thursday 2018-03-08 at 18:27 > *To: *"ripe-atlas at ripe.net" <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 > -- *Marcel Flores, PhD* | Research Scientist VerizonDigitalMedia.com | AS15133 <https://www.peeringdb.com/asn/15133> p: +1 310.593.6880 e: marcel.flores at verizondigitalmedia.com 13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20180308/ff53f0d4/attachment.html>
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] API Keys problem?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]