Summary

  • At RIPE 93 on 28 October, RIPE NCC said OpenID Connect had gone live that morning for its RPKI Dashboard. The old shared cookie was to remain through the day so existing users could finish their sessions.
  • The same engineer said the RPKI Management API still used a shared secret without an expiry date. A replacement tied to SSO accounts, with a one-year lifetime, remains in the plan.

The browser door changed on Wednesday morning. The automation door did not. Tim Bruijnzeels, reporting for RIPE NCC at the Routing Working Group, described a newly live OIDC login for the RPKI Dashboard and then turned to an API credential that still has no expiry. Those are two routes to changing routing-security assertions, and their clocks are now different.

The old browser cookie had a final scheduled shift. Bruijnzeels said RIPE NCC had already mitigated the Dashboard part of a previously reported login issue, but needed OIDC for the next step. The shared cookie was still present during his talk and was due to remain until the end of 28 October to avoid throwing existing users out mid-session. That choice gave continuity a price measured in hours, with a stated cutoff rather than an indefinite exception.

The Q4 RPKI plan had put Dashboard OIDC and API-key replacement in one work item. The meeting update separated them. Existing API access, Bruijnzeels said, rests on a no-expiry shared secret configured in the LIR portal. It is available to LIRs; holders of PI or legacy resources working through a sponsoring LIR do not have that API route. RIPE NCC wants SSO-linked keys with one-year lifetimes, renewal and expiry warnings, and access for those end users. It has not announced a production cutover for the keys.

The API is a real operating surface: RIPE NCC's developer guide documents an X-API-Key credential and a ROA publication call. A fresh browser login cannot retire that credential on behalf of the scripts that use it. The public record still lacks a post-28 October cookie-retirement receipt and a dated API-key cutover; RIPE NCC's closeout for each path would settle the two dates.