A single target system goes offline
Users may see that requested operations, such as password changes, have not happened yet. You can run system operation reports; for example to see which password have been expired and not changed recently. You can also review logs to detect failed password reset attempts in the form of connectors errors.
A server monitoring system may be able to localize the problem and identify a failed server as opposed to a failed network link.
A recommended way to detect this condition and related problems is to configure events to trigger email or update tickets in the event of a failed operation.
What stops working | What continues to work | Possible Causes | Data loss | Resolution |
|---|---|---|---|---|
The main Bravura Security Fabric servers will be unable to scramble passwords on the device which is offline. | Users can still log into Bravura Security Fabric , assuming they are not authenticating against the offline target through. They can access their profiles and carry out tasks that do not require a connection to affected target systems. Moreover, users who access the system via Bravura Security Fabric will be unable to connect to the system itself, or at least not over the network. It is possible that a checked out password will be used to assist in system recovery at the failed device’s console, however. | A system where Bravura Security Fabric performs operations goes offline. This may be for a variety of reasons, including:
| None, unless an extremely unlikely race condition takes place:
| Repair the failed device as soon as possible. |