Pattern Matching
In an unfortunate situation, albeit a real one, if you don't have a common attribute value to correlate the account, say account 'jdoe123' with the identity of 'John Doe' it belongs to, you can use a real solution called "Pattern Rule Matching".
e.g: 'jdoe123' follows a pattern "First Character of First Name + Last Name + random numeric string"
Note: Penrose can use multiple patterns, and will use of them all as necessary.
However, this pattern will work on a John Doe and a Jane Doe in the environment, both of which will get identified based on the above pattern.
When these cases happens, Penrose Studio can provide a reconciliation wizard tool to detect these exception as part of the deployment. Using this, the administrators in charge can be notified of these exception conditions, and they can examine the data, do their own investigation, and take appropriate action.
This can be turned into a unique end-user driven account claim process, that helped them clean up extraneous accounts in their systems quite rapidly, thus achieving a key goal in their compliance plans.