Back to overview
Maintenance

SSL Certificate Update for *.namirialtsp.com Endpoints

Apr 28 at 10:00pm CEST  –  Apr 29 at 12:00am CEST
Affected services
CA services
Identity Services (SPID)
Onboarding
SMS Service
SWS Saas
Email Gateway PROD
Whatsapp Gateway
SWS Legacy
Portal
Lean Disposable
ESP Saas

Maintenance
Apr 28 at 10:00pm CEST

Dear Customers,
As part of our scheduled infrastructure maintenance activities, please be informed that on April 28, during the time window 22:00 – 24:00 (CET), we will perform an update of the SSL certificate for the *.namirialtsp.com endpoints.
This update is required because the current certificate is approaching its expiration date.
The activity has been planned to ensure service continuity and to maintain the security standards of the infrastructure. No service disruption is expected during this operation.
Please note that the new certificate will be issued by a Certification Authority (CA) different from the one currently in use.
The new Root CA will be the following:
https://www.amazontrust.com/repository/AmazonRootCA1.pem
Customers who have application integrations with our endpoints and use certificate pinning are kindly requested to review their configurations and, if necessary, update the pinning values to reference the new Root CA.
As indicated in Amazon’s official guidelines, certificate pinning should be configured only on the Root CA and not on Intermediate CAs, in order to avoid potential issues related to the dynamic rotation of intermediate authorities.
For further details:
https://aws.amazon.com/it/blogs/security/amazon-introduces-dynamic-intermediate-certificate-authorities/
To help determine whether certificate pinning is used in your integrations, we recommend verifying whether:
your applications or client libraries are configured with specific certificates, fingerprints, or public keys associated with the *.namirialtsp.com endpoints;
custom trust stores or TLS configurations are in place that explicitly restrict the accepted Certification Authorities;
certificate validation or pinning mechanisms have been implemented directly at the application level.
If your integrations rely solely on the standard operating system or TLS library trust store, without custom certificate validation or pinning configurations, no action is normally required.
For any additional information or support requests, our team remains available through the usual support channels.