
In this article
- What changes, and when?
- What happened to the Smart-ID certificate on 6 October?
- Which TLS cipher suites are allowed from 2 November?
- Which systems are most likely to break?
- How do I test my server against the demo environment?
- What do Smart-ID+ and NFC registration mean for a portal?
- Checklist for direct-integration owners
What changes, and when?
| Date | Change | Impact on a direct integration |
|---|---|---|
| 30 Sep 2026 | New certificate on the demo host sid.demo.sk.ee | Test environments needed the new certificate |
| 6 Oct 2026, 13:00 EEST | New Smart-ID RP API certificate in production | Without it, Smart-ID authentication and signing no longer work in your service |
| Already live in demo | Strong TLS cipher suites only | You can test today whether your server can connect |
| 2 Nov 2026 | Strong TLS ciphers only on production Smart-ID and Mobile-ID APIs | Old Java, .NET or OpenSSL set-ups will fail to connect |
| Gradually in 2026 | Smart-ID+ (QR code on desktop, app-to-app on mobile) | Appears in a service once its provider is technically ready |
| Since 22 Sep 2026 | Smart-ID registration with a Latvian eID card over NFC | More people can create a Smart-ID account without a bank |
What happened to the Smart-ID certificate on 6 October?
At 13:00 EEST on 6 October 2026 SK ID Solutions replaced the Smart-ID RP API service certificate; the demo host sid.demo.sk.ee switched on 30 September. SK warned that e-service providers who did not add the new certificate would not be able to use Smart-ID for authentication and signing.
If your Smart-ID login has returned connection or certificate-validation errors since that afternoon, this is the likely cause. End users’ apps were not affected; the fault is on your server side.
The fix: download the new certificate (PEM or DER) from the SK notice and add it wherever your system keeps trusted Smart-ID certificates – SDK configuration, Java keystore or application settings. Check the DigiCert issuing certificates SK refers to as well.
Which TLS cipher suites are allowed from 2 November?
From 2 November 2026 the production Smart-ID and Mobile-ID APIs accept only these suites:
TLS 1.3: TLS_AES_256_GCM_SHA384. TLS 1.2: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 or TLS_DHE_RSA_WITH_AES_256_GCM_SHA384. In OpenSSL naming the TLS 1.2 suites are ECDHE-RSA-AES256-GCM-SHA384 and DHE-RSA-AES256-GCM-SHA384.
The restriction is already enforced in demo. If your integration works against demo today, production on 2 November should be fine; if demo fails, production will fail the same way.
Which systems are most likely to break?
The rule applies to your server’s outbound connections to SK. Old runtimes where AES-256-GCM or ECDHE is missing or disabled are most at risk:
- Java 7 and older – SunJSSE has no GCM suites. Java 8 builds before 8u161 needed the “unlimited strength” policy for AES-256. TLS 1.3 arrived in Java 11 and 8u261.
- .NET Framework on older Windows Server – .NET uses the operating system’s Schannel cipher list; on older Windows Server versions the required suites may be missing or disabled by group policy.
- OpenSSL 1.0.0 and older – GCM support came in OpenSSL 1.0.1, TLS 1.3 in 1.1.1. This covers PHP, Python, Ruby and anything else using the system OpenSSL.
- Hand-tuned cipher lists – if an admin once restricted ciphers to AES-128 or CHACHA20, they will no longer match SK.
- Proxies and TLS inspection – if outbound traffic passes through a proxy that terminates TLS, check that too.
How do I test my server against the demo environment?
Run these on the server that calls Smart-ID. openssl s_client tests that machine’s OpenSSL; on success the output shows Cipher is ... with the negotiated suite. Java and .NET apps do not use OpenSSL, so for them the decisive test is a real Smart-ID login from your app against demo.
# TLS 1.2 with ECDHE (OpenSSL 1.0.1+)
openssl s_client -connect sid.demo.sk.ee:443 -servername sid.demo.sk.ee \
-tls1_2 -cipher ECDHE-RSA-AES256-GCM-SHA384 </dev/null
# TLS 1.2 with DHE
openssl s_client -connect sid.demo.sk.ee:443 -servername sid.demo.sk.ee \
-tls1_2 -cipher DHE-RSA-AES256-GCM-SHA384 </dev/null
# TLS 1.3 (OpenSSL 1.1.1+)
openssl s_client -connect sid.demo.sk.ee:443 -servername sid.demo.sk.ee \
-tls1_3 -ciphersuites TLS_AES_256_GCM_SHA384 </dev/null
# Which suites the SK server accepts
nmap --script ssl-enum-ciphers -p 443 sid.demo.sk.eenmap shows what SK accepts, not what your application supports. If at least one openssl command succeeds, the system OpenSSL is ready.What do Smart-ID+ and NFC registration mean for a portal?
Smart-ID+ is a safer flow: on a computer the user scans a dynamic QR code in the Smart-ID app; on a phone the app opens automatically and returns the user to your app or browser after the PIN. No personal code entry, and an action can be approved only if it started on the user’s own device.
SK is rolling Smart-ID+ out gradually, “depending on the technical readiness of service providers”. For a direct integration that means you build the QR display and app-to-app hand-off yourself; until the rollout completes, the old flow keeps working.
Since 22 September 2026 people can create a Smart-ID account by reading their Latvian eID card over NFC. That widens Smart-ID beyond internet-bank customers – one more reason to offer it alongside eParaksts.
Checklist for direct-integration owners
Check the certificate
Has Smart-ID login worked in production since 6 October 2026? If not, add the new SK certificate.
Check the runtime version
Note the Java, .NET or OpenSSL version and cipher configuration on the server that calls the Smart-ID API, proxies included.
Test against demo
Run the commands above and complete a full Smart-ID login against
sid.demo.sk.ee.Fix by 1 November
Upgrade the runtime or enable at least one of the three allowed suites. Questions to SK: support@skidsolutions.eu.
Plan for Smart-ID+
Schedule the QR and app-to-app flow so users no longer type their personal code.