Do not double target
Double-targeting is not supported. As mentioned in question 8 of Planning target systems the Bravura Security Fabric database should contain unique objects.
Collecting the same objects (accounts, groups, memberships, attributes) from separate target objects that target the same system can cause serious workflow, data storage or application functionality issues.
If more than one target has to be added for the same Bravura Security Fabric -managed system, put in place operational and functional barriers to prevent the same object being listed more than once. The application itself attempts to prevent this situation; for example, if the address configuration lists accounts from the same target more than once, neither of the copies will be loaded and warnings about the issue are logged during auto discovery.
In other cases Bravura Security Fabric cannot prevent the situation for lack of data; for example:
In Bravura Privilege if the same target is managed once via its IP and again targeting via IP, Bravura Privilege cannot tell that the two targets are the same system.
Targeting via IP is not generally recommended as IP numbers can change, making the systems unreachable, or even worse, mixing up one system's historical/Audit data with another.
Similarly, onboarding the same system in LWS and PUSH modes will cause data issues.
Privilege can't find the duplicates because the two modes are handled as different data sets.