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/db-wg@ripe.net/
[db-wg] db-wg Digest, Vol 66, Issue 3
- Previous message (by thread): [db-wg] db-wg Digest, Vol 66, Issue 3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Schulze
andreas.schulze at datev.de
Mon Feb 20 14:29:44 CET 2017
Am 20.02.2017 um 07:49 schrieb Alexander Stranzky: >> 2. How are updates authenticated? >> I'm aware, each object has a "mntner" but how and where is the Maintainer identity part of request to the API? > > Authentication is done via the maintainer's password. > >> 3. the Test-DB did not contain any objects related to our company - that's OK. >> But could I add them? And how? I guess I may use 'https://apps-test.db.ripe.net/search/lookup.html?source=test&key=TEST-NCC-HM-MNT&type=mntner' >> Right? > > There is the test database maintainer (TEST-DBM-MNT) you can use to set > up everything using the password "emptypassword". once you have your own > maintainer set up, use that one. > > see also > https://github.com/RIPE-NCC/whois/wiki/WHOIS%20REST%20API%20Migration%20Guide > > Regards, > Alexander Stranzky > Thanks, just created a person and a mntner object :-) The Documentation is misleading. https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/10-authorisation/10-1-authorisation-model say: Example: auth: MD5 $1$a..." but it should say Example: auth: MD5-PW $1$a..." -- A. Schulze DATEV eG
- Previous message (by thread): [db-wg] db-wg Digest, Vol 66, Issue 3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]