Continued improvements have meant that we do not need to fall back to the previous database structure. We will continue to keep a careful eye on enrollment activity over the coming days
Mar 22, 21:17 UTC
Authentication is stable. Following a hotfix last night we have seen a significant performance improvement. The number of customers experiencing enrolment issues has also reduced significantly.
Mar 22, 11:51 UTC
Update - Authentication is still stable. A fix to Token Management is implemented to address Unlock use case. We still see some successes and some failures with new token enrollment.
Mar 21, 04:58 UTC
Authentication is still stable and we still see some successes and some failures with new token enrollment. We are also working on a fix for token management (token unlocks etc.).
Mar 20, 22:16 UTC
Authentication is still stable and we still see some successes and some failures with new token enrollment. Token management is also being investigated.
Rather than change the overall status of this issue to Green I have chosen to keep it as yellow while we are carefully monitoring the service and doing everything needed to ensure authentication stability is maintained.
We are working through a number of options to achieve a longer term fix and are testing each of them to ensure we achieve the best possible result.
I will provide a further update when we need to. In the meantime we really appreciate your continued patience.
Mar 20, 14:00 UTC
Authentication continues to be stable and we still see some successes and some failures with new token enrollment. Our teams are working on a number of different paths to restore token management functions such as unlocking tokens etc.. The current plan is that before the European morning we will reverse the update that was made on Saturday. We are trying to do this with minimal impact on customers and token holders.
If you experience any issues please raise a support ticket.
Mar 20, 01:04 UTC
All types of authentication have been stable for a number of hours. We are actively managing this by moving back and forth between two copies of the database as required. However, we still see the occasional enrollment failure but all other parts of the service are working well.
We have supplemented our team with a number of DBA's from other parts of Gemalto and they have already come up with some proposals for us which are in development and can potentially be deployed as hotfix's.
Mar 19, 21:32 UTC
Intermittent failures observed with authentications. A fix is currently being tested for implementation.
Mar 19, 15:42 UTC
We have rolled database services to a secondary node and partial service will be resumed across all services whilst we work towards a permanent resolution.
Mar 19, 14:36 UTC
We are momentarily stopping enrollment to restore authenticaiton to full functionality
Mar 19, 14:00 UTC