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/[email protected]/
[ncc-services-wg] RIPE NCC Access 2FA
- Previous message (by thread): [ncc-services-wg] Enforce 2FA for RIPE NCC Access account (Hank Nussbacher)
- Next message (by thread): [ncc-services-wg] The redesigned www.ripe.net is now live
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Potvin
peter at accuris.ca
Thu Jan 11 00:36:10 CET 2024
Dear List, I'm glad to see that RIPE NCC has followed in ARIN's footsteps regarding the enforcement of two-factor authentication. I have a few questions regarding this that I'm sure quite a few members of the NCC community also have. 1. Is this for all NCC Access accounts or only applicable to LIRs/end users with PI resources? 2. Will there be an option for multiple YubiKeys or U2F keys for authentication, asides from the current TOTP option? If so, is there an ETA for when this would be implemented? 3. Will RIPE NCC have secondary 2FA requirements for high-risk transactions like RPKI issuance/revocation and delegation, requiring users to re-authenticate when performing these actions? If so, would this change anything with regards to the API implementations? Regards, Peter Potvin | Executive Director ------------------------------------------------------------------------------ *Accuris Technologies Ltd.* -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ncc-services-wg/attachments/20240110/b77c45e1/attachment.html>
- Previous message (by thread): [ncc-services-wg] Enforce 2FA for RIPE NCC Access account (Hank Nussbacher)
- Next message (by thread): [ncc-services-wg] The redesigned www.ripe.net is now live
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]