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]/
[db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
- Previous message (by thread): [db-wg] RIPE Database Release 1.72 - including SSO Integration
- Next message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Mon Mar 24 14:27:39 CET 2014
Dear Colleagues The RIPE Database release 1.72 has now been fully deployed to production. We would like to point out that, with this release, Webupdates and Syncupdates can only be accessed with HTTPS and not with HTTP. This is to conform to the requirements of using RIPE ACCESS now as an authentication method for updating the RIPE Database. Any update using HTTP will be automatically redirected to HTTPS. Regards Denis Walker Business Analyst RIPE NCC Database Team -------- Original Message -------- Subject: RIPE Database Release 1.72 - including SSO Integration Date: Thu, 06 Mar 2014 17:15:16 +0100 From: Denis Walker <denis at ripe.net> Organization: RIPE NCC To: Database WG <db-wg at ripe.net>, NCC Services WG <ncc-services-wg at ripe.net> Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20140324/b894ecee/attachment.html>
- Previous message (by thread): [db-wg] RIPE Database Release 1.72 - including SSO Integration
- Next message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]