Based in Amsterdam
Articles
Likes on articles
I'm a Senior Technical Analyst with the RIPE NCC, working on Whois and the RIPE database.
Email: eshryane@ripe.net
• 5 min read
Proposed at RIPE 91 in the Address Policy Working Group and then further discussed in the Database Working Group, the reg-nr: attribute (NWI-21) has already been implemented ahead of RIPE 92, showing how quickly community input can lead to practical results. It adds official company registration nu…
• 3 min read
We are extending the API key model introduced for the RIPE Database to create a more consistent, secure, and flexible approach across RIPE NCC services.
• 11 min read
New requirements for bulk email senders are changing the way we do email. In this article, we give an update on what those changes look like and how we'll be implementing them.
• 5 min read
Defining the criticality of RIPE NCC services provides a whole range of benefits. In this article, we take a look at the model we're adopting in order to determine a criticality rating for our services.
• 6 min read
We’ve been brainstorming on a process to determine the criticality level of our services, and we’d now like to ask the community for input on how we should approach this effort moving forward.
• 6 min read
Thousands visit the RIPE Database web interface every day to seek out information on Internet number resources. After taking a closer look at how people interact with the interface, we've come up with four small changes that, without altering the way you search, could very well cut down on the amou…
Showing 6 article(s)
“Only allowing keys to last a year is unreasonable. I suggest you should allow keys to have expiry of a few years (or even not expire at all), but require them to be locked-down to specific IPs. Also, PLEASE make sure you have robust email warnings for upcoming key expiration. This will likely break a lot of people's update scripts when they inevitably forget to refresh their API keys each year.”
Hello Charlie, thanks for your feedback. The 1 year expiry requirement was discussed last year: https://mailman.ripe.net/archives/list/db-wg@ripe.net/thread/CAT5DHOTRPU4YJJ22AT2BOPTYDSTCM5A/#2HRL43LB3L5FCSYBSA3R2BVFB54MILRN. The RIPE NCC Access service will send an email to the email address 2 weeks before an API key is due to expire. I suggest that users also make a calendar entry or similar reminder before a key expires. You can see when a key expires on the API keys page.
“Some legacy software still use password as HTTP query parameter will this still work? So if I generate and then use username & password can it be used as HTTP query parameters?”
Hi Tomaž any software that uses password authentication will need to be updated to use an alternative: https://docs.db.ripe.net/Authorisation/Authorisation-Model API keys are meant to be a "drop-in" alternative to passwords, by replacing the password query parameter with a HTTP Authorisation header, or use the HTTP client's username / password flags (e.g. for curl it's -u or --user).
“Fantastic to see this live Ed and thank you to you and the team for making it happen. Is there a full documentation page for the API by chance? Specifically, I'd like to know if the rest API supports updates via application types other than XML?”
Thanks Mick, that's a good idea. I'll update the appendix on API keys in the DB documentation : https://docs.db.ripe.net/Appendices/Appendix-K--API-Keys/
Hello David, unfortunately, the beta syncupdates page does not support the dry-run parameter. This is a bug that we should fix. in the meantime, please click "Switch to classic syncupdates" on the top right side of the page, in order to use the dry-run flag. Regards Ed Shryane RIPE NCC
Showing 4 comment(s)