All Systems Operational
About This Site
Welcome to the SafeNet Trusted Access status site. Included in this site is an option to subscribe to live service updates as well as see history of our service availability.
RADIUS Service
Operational
RADIUS Service (standard)
Operational
RADIUS over IPsec (custom subscription)
Operational
STA Token Management Console
Operational
STA Access Management Console
Operational
SAML and OIDC Service
Operational
Management API (BSIDCA)
Operational
Authentication API (Token Validator)
Operational
Push OTP Service
Operational
Self-Enrollment
?
Operational
Self-Service and User Portal
?
Operational
Synchronization Service
Operational
Risk Engine
Operational
VPN UK
Operational
VPN Canada
Operational
Audit Logging
Operational
Policy Engine
Operational
Identity Provider
Operational
Auto-Provisioning Service
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Quaterly Failover Resiliance Testing
Jan 25, 14:00-17:00 UTC
SafeNet Trusted Access Quarterly Failover Test - Classic
In our ongoing pursuit of service stability and resilience, we will be performing our quarterly Failover Test in the Classic environment on January 25th, 2020 between the hours of 14:00 UTC and 17:00 UTC
During this period, brief outages up to an expected maximum of 15 minutes will occur at the beginning and near the end of the window as we conduct the failover and failback. It is also possible for some service degradation to be experienced in terms of service responsiveness and performance as we conduct testing exercises within the window.
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 hardcoded IP Addresses for Token Validator:
Our Disaster Recovery Plan is designed to leverage DNS to ensure a smooth and rapid failover of services. As such, during failover 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 hardcoded IP addresses.
Our next DR test is scheduled for the second quarter of 2020, so it is highly advisable to rectify this before that time, to ensure maximum service availability.
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=b7af9a474f1cbfcc102400818110c77e
Please 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.
Gemalto Authentication and Access Management Cloud Services
Posted on Jan 17, 17:17 UTC
In our ongoing pursuit of service stability and resilience, we will be performing our quarterly Failover Test in the Classic environment on January 25th, 2020 between the hours of 14:00 UTC and 17:00 UTC
During this period, brief outages up to an expected maximum of 15 minutes will occur at the beginning and near the end of the window as we conduct the failover and failback. It is also possible for some service degradation to be experienced in terms of service responsiveness and performance as we conduct testing exercises within the window.
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 hardcoded IP Addresses for Token Validator:
Our Disaster Recovery Plan is designed to leverage DNS to ensure a smooth and rapid failover of services. As such, during failover 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 hardcoded IP addresses.
Our next DR test is scheduled for the second quarter of 2020, so it is highly advisable to rectify this before that time, to ensure maximum service availability.
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=b7af9a474f1cbfcc102400818110c77e
Please 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.
Gemalto Authentication and Access Management Cloud Services
Posted on Jan 17, 17:17 UTC
