Read-only view: browsing is open, changes need a signed-in user.
Staging: test environment for new releases. Data may be reset; do not share from here.
WatchtowerSignicat competitor intelligence

Feed

Reset
SK ID Solutions / Smart-ID· 7 Sep 2026 L2 · Minor

SK ID Solutions states the TLS cipher suite change is implemented in demo environments and planned for production endpoints on 2 November 2026.

Mobile-ID and Smart-ID endpoint Change on 2 November 2026 ↗

What happened

  • Only strong, modern cipher suites will be accepted for TLS connections, and older and weaker cipher suites are disabled.
  • Supported TLS 1.3 suite listed is TLS_AES_256_GCM_SHA384; supported TLS 1.2 suites are ECDHE-RSA and DHE-RSA with AES-256-GCM-SHA384.

Why it matters to Signicat

  • Integrations relying on older TLS configurations may break at the production cutover, creating migration work for Smart-ID and Mobile-ID relying parties, including Signicat-run integrations if any exist (unverified).
Evidence from the source (3 quotes)
  • “Only strong, modern cipher suites are now accepted for TLS connections.” source ↗
  • “\* TLS\AES\256\GCM\SHA384” source ↗
  • “However, it may affect integrations that rely on older TLS configurations that do not support the cipher suites listed above.” source ↗
eID brokeringFeature updateNordicsUK IECEE

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5