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] API keys for database maintenance
- Previous message (by thread): [db-wg] API keys for database maintenance
- Next message (by thread): [db-wg] API keys for database maintenance
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Fri Feb 21 13:28:31 CET 2020
* 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
- Previous message (by thread): [db-wg] API keys for database maintenance
- Next message (by thread): [db-wg] API keys for database maintenance
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]