[ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Previous message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Next message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Band
alexb at ripe.net
Wed Dec 4 15:25:02 CET 2013
Hi Daniel, On 4 Dec 2013, at 14:45, Daniel Stolpe <stolpe at resilans.se> wrote: > On Wed, 4 Dec 2013, Sander Steffann wrote: > >> Hi, >> >>> We would like to propose to put this functionality in maintenance mode, meaning that it would be provided as it is without a service guarantee. Alternatively, it could be removed altogether. This would free us of a maintenance and support burden, meaning that we can spend these resources on other valuable services. >> >> I wouldn't mind if it was removed completely. > > +1. > > Do we know if these users rely solely on X.509 or do they have other options? Everybody who has an X.509 certificate for RIPE NCC Access login also has a username and password. You can use either method to log in at all times. Cheers, Alex
- Previous message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Next message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]