How does Blueprint 3.5 handle usernames when installed on a site with multiple domains where the username is present in both domains?

How does Blueprint 3.5 handle usernames when installed on a site with multiple domains where the username is present in both domains?

Blueprint will install and operate in a multi-domain environment, but will treat equal username from different domains as if they are the same. Blueprint does not capture domain information for network accounts when we are logging jobs at Workstation or as part of Secure Release. 

As an example print tracking for username "matt" on "CORP" domain and "matt" on the "LEGAL" domain will be logged against a single user identifier i.e to "matt". Likewise with Secure Release all jobs submitted by "matt" on the "CORP" domain and "matt" on the "LEGAL" domain will be displayed at terminal if either account is used to logon at the device.

Pharos’s understands that if the Domains are in the same Forest, then the account is actually unique within the global catalogue and "matt" on the "CORP" domain and "matt" on the "LA" domain identify the same user. Authentication scripts can be configured to use the local domain controller to the server running the authentication script (or possibly the global catalogue).

If, however, the Domains are in different Forests and "matt" on the "CORP" domain and matt on the "LA" domain identify two different people, then we have a problem, particularly with Secure Release. To work around that issue is to separate and distinguish between accounts "matt" on the "CORP" domain and "matt" on the " LA" domain we would need an Analyst and set of Collectors per Forest. The installation of the Analyst and its Collectors would then operate independently, ensuring the Secure Release operated smoothly.