Completed -
The scheduled maintenance has been completed.
Feb 20, 17:00 UTC
Update -
All Services now running on Primary site without issue. We will continue to monitor for continued stability.
Feb 20, 16:59 UTC
Update -
Primary Authentication services are now running from the Primary site without issue.
Feb 20, 16:48 UTC
Update -
Commencing failback to primary site.
Feb 20, 16:44 UTC
Update -
All STA Services are failed over to DR site and running without issue.
Observation and testing is underway.
Feb 20, 14:28 UTC
Update -
Primary Authentication services have now been failed over to DR site and are running without issue.
Feb 20, 14:04 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 20, 14:01 UTC
Scheduled -
In our ongoing pursuit of service stability and resilience, we will be performing our quarterly Failover Test in the Classic environment on February 20th, 2021 between the hours of 14:00 UTC and 17:00 UTC. During this period, brief outages of 1-2 minutes up to an expected maximum of 15 minutes will occur at the beginning and near the end of the window as we conduct the fail-over and fail-back.
Complete service availability and performance will resume at the end of the window.
Updates will be provided via our Statuspage:
https://status.sta.safenetid.com/NOTE: For those who use hard-coded IP Addresses for Token Validator:
Our Disaster Recovery Plan is designed to leverage DNS to ensure a smooth and rapid fail-over of services. As such, during fail-over exercises (planned or unplanned) could cause service disruption for your users for authentication if you are to continue to use hard-coded IP addresses. It is expected that during the upcoming test, disruption times could be longer than the above-mentioned 15 minutes for those with hard-coded IP addresses.
Further, as public IP addresses can be changed by the Internet Service Provider, this can increase the risk of disruption, as well as create administrative overhead for your team.
We strongly encourage the use of our FQDN: agent1.safenet-inc.com or agent2.safenet-inc.com.
If you have any questions as to how to properly add the DNS entries, we recommend using this guide as a reference:
https://supportportal.thalesgroup.com/csm?id=kb_article_protected&sys_id=b7af9a474f1cbfcc102400818110c77ePlease note, that accessing this link does require an active Thales Support Portal account.
If you have any questions or concerns, please reach out to our Client Services team:
•
https://safenet.gemalto.com/technical-support/• United States: 800-545-6608
• International: +1-410-931-7520
We thank you for your continuous support and cooperation.
Thales Authentication and Access Management Cloud Services
Feb 12, 18:15 UTC