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/ripe-atlas@ripe.net/
[atlas] Automating software probe creation?
- Previous message (by thread): [atlas] Automating software probe creation?
- Next message (by thread): [atlas] Automating software probe creation?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Colin Johnston
colinj at mx5.org.uk
Mon Jan 4 13:42:19 CET 2021
And automated up probe alerting needed as well :) Yours bt techie Sent from my iPod > On 4 Jan 2021, at 11:57, Carsten Schiefner <carsten at schiefner.de> wrote: > > Hi, Philip - > > a happy new year to you and everybody here on this list, first of all! > >> On 04.01.2021 11:53, Philip Homburg wrote: >> We are working on an API. However, the only thing the API will do is to copy the public key to the atlas backend systems. You still have go to the web size, log in, etc. We want to associate a user with each probe. > > IANAP and therefore probably miss a crucial point here: but can't user identification, authentication and so also probe-to-user association be done via an API, too? > > Best, > > -C. >
- Previous message (by thread): [atlas] Automating software probe creation?
- Next message (by thread): [atlas] Automating software probe creation?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]