[db-wg] API keys for database maintenance
- Previous message (by thread): [db-wg] API keys for database maintenance
- Next message (by thread): [db-wg] Update RIPE MNT records
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Fri Feb 21 13:36:08 CET 2020
Hi, I am against this proposal unless any other arguments can be made, as I believe that the NCC's resources can be better used doing other things. (I would think that this would require quite a large amount of work due to how split the DB and LIR portal are.) - Cynthia On Fri, Feb 21, 2020 at 1:28 PM Tore Anderson <tore at fud.no> wrote: > * Cynthia Revström > > > But it does have something very similar, md5-pw and I really don't see > why this is not adequate. > > Just generate a 64 character hex string put it as a password and boom > you have an API key. > > > > My question is, how would having a dedicated API key feature help? > > The API keys system in the LIR portal is much easier to use. You can very > easily issue and revoke API keys, see which keys are already active, who > issued them and when, etc. > > It does not make sense to me for the RIPE database APIs to not participate > in this system. > > Again, and to be absolutely clear, I do not propose to remove the MD5-PW > authentication method. If you are using it and you are happy with it, then > rest assured that this proposal will not take anything away from you. > > Tore > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20200221/421c7f52/attachment.html>
- Previous message (by thread): [db-wg] API keys for database maintenance
- Next message (by thread): [db-wg] Update RIPE MNT records
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]