[db-wg] Updating the database via HTTP API - best practices

• Previous message (by thread): [db-wg] Updating the database via HTTP API - best practices
• Next message (by thread): [db-wg] Draft Agenda RIPE75 - Database Working Group

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Alexander Stranzky astranzky at velia.net
Thu Apr 12 09:40:41 CEST 2018

> What is the current best practice for handling Auth on HTTP API updates to the RIPE database, and is there a roadmap for change that I can consider as I write my tools to publish and maintain objects?

Same situation here on my end. Anyways, I'd love to have an
authentication method that uses one of my existing RIPE DB key-cert
objects (maybe something like an HMAC).

Cheers, Alex

-- 
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau
Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588
Tel: +49 6181 1898119 * http://www.velia.net
Follow us on twitter: https://twitter.com/velia_net

• Previous message (by thread): [db-wg] Updating the database via HTTP API - best practices
• Next message (by thread): [db-wg] Draft Agenda RIPE75 - Database Working Group

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]