itsmeDigitalID incident

itsme® Incident - Client Secret only

Critical Resolved View vendor source →

itsmeDigitalID experienced a critical incident on February 2, 2024 affecting Production - Identity - OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more component, lasting 24m. The incident has been resolved; the full update timeline is below.

Started
Feb 02, 2024, 09:32 AM UTC
Resolved
Feb 02, 2024, 09:57 AM UTC
Duration
24m
Detected by Pingoru
Feb 02, 2024, 09:32 AM UTC

Affected components

Production - Identity - OIDC private key JWTProduction - Identity - OIDC private key JWTProduction - Qualified Electronic Signature - OASIS DSSProduction - Qualified Electronic Signature - OASIS DSSProduction - Account ManagementProduction - Account Management

Update timeline

  1. investigating Feb 02, 2024, 09:32 AM UTC

    Dear Partner, We currently encounter an issue with Partners using Client Secret. Our technical teams are investigating and working on a solution to resolve the issue as fast as possible. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]

  2. resolved Feb 02, 2024, 09:57 AM UTC

    Dear Partner, A solution has been rolled out and the service has been restored. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]