[service] Scheduled Downtime for RIPE NCC Access (SSO)
Dear colleagues, RIPE NCC Access (SSO) will be unavailable next Wednesday, 7 June, from 15:00-17:00 UTC. We will be using this downtime to replace our existing SSO back end with Keycloak. This will make it easier for us to provide additional features in the future, such as SSO integration with other platforms, additional multi-factor authentication options, and improved security in general. Thank you for your understanding. Kind regards, Theo -- Theodoros Polychniatis Manager Business Applications RIPE NCC
Dear colleagues, This is a reminder that RIPE NCC Access (SSO) will be unavailable today (Wednesday, 7 June) from 15:00-17:00 UTC. We will be using this downtime to replace our existing SSO back end with Keycloak and deploy it to the Kubernetes cluster in AWS (EKS). Further information on this subject can be found in the "Registry and Technology Update" presented at RIPE 86: https://ripe86.ripe.net/wp-content/uploads/presentations/97-RIPE-86-Registry... Kind regards, Theo -- Theodoros Polychniatis Manager Business Applications RIPE NCC -------- Forwarded Message -------- Subject: [service] Scheduled Downtime for RIPE NCC Access (SSO) Date: Wed, 31 May 2023 17:03:08 +0200 From: Theodoros Polychniatis <tpolychnia@ripe.net> To: ncc-announce@ripe.net Dear colleagues, RIPE NCC Access (SSO) will be unavailable next Wednesday, 7 June, from 15:00-17:00 UTC. We will be using this downtime to replace our existing SSO back end with Keycloak. This will make it easier for us to provide additional features in the future, such as SSO integration with other platforms, additional multi-factor authentication options, and improved security in general. Thank you for your understanding. Kind regards, Theo -- Theodoros Polychniatis Manager Business Applications RIPE NCC
participants (1)
-
Theodoros Polychniatis