Tore Anderson wrote on 20/09/2024 12:34:
To be clear, I do not see this as an either/or - having the option for
creating API keys both at the LIR level *and* at the user level would be
ideal, in my opinion.
In theory that would be nice, but in practice sounds like it would mean
adding an extra layer into the authentication model for LIR
authentication, in addition to the existing account-based authentication
system. Keeping a single layer via using an api-only account would
normally keep the architectural model cleaner.
But: keeping the architectural model simpler isn't the same as keeping
the implementation model easier.
Not wanting to back-seat drive or anything, but I'm a major fan of
maintainable codebases.
Nick
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
