[ncc-services-wg] Proposed Implementation for Two-Factor Authentication

Dear colleagues,

Firstly, I would like to thank all who provided feedback on our authentication proposal for RIPE NCC Access. Many responded to the request for feedback, both publicly and privately, which is very encouraging to see.

Based on your input, and the fact that this functionality is very rarely used, we would like to propose the following:

1. Discontinue X.509 identity certificate login from 1 February 2014
- All users who currently have a certificate will be contacted individually
- Users will only use their RIPE NCC Access username and password to log in from 1 February 2014
- Note: a lost password can be recovered at
https://access.ripe.net/forgot-password

2. Build an implementation for two-factor authentication for RIPE NCC Access, supporting at least:
- HMAC-Based One-Time Password (HOTP)
- Time-Based One-Time Password (TOTP)

We would like to plan the development effort and scheduling before the end of the year and inform you about our roadmap once the project plan is in place.

Please let us know if you have any comments or questions.

Kind regards,

Alex Band
Product Manager
RIPE NCC