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] 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 ]
Philip Homburg
philip.homburg at ripe.net
Mon Jan 4 13:11:55 CET 2021
On 2021/01/04 12:57 , Carsten Schiefner wrote: > 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? That may become too complex. RIPE NCC currently has no API that allows a user to log in. Logging in goes through a web form. What we can do (in theory) is support logging in through a web form and then creating an API key for probe registration (similar to keys we have for creating measurements). Then the user can install the API key on the probe and then register the probe using an API. However, that seems overly complex. In addition it would be nice to name a probe, give it a location. So there is a need to go to the website anyhow. Of course it can be requested as feature. If there are good use cases, we can put it on the list of things to look at. Philip
- 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 ]