Your scenario involves the complexities of cross-forest authentication and authorization mechanisms. Here's a detailed overview of your questions:
- Use of Referrals (crossRef objects) for Cross-Domain Group Membership:
- While it's feasible to set up cross-forest trusts and allow users from one forest (Forest A) to access resources and potentially be added to groups in another forest (Forest B), the direct use of referrals (crossRef objects) for the purpose you're describing is not typically how this is achieved in an Active Directory (AD) environment.
- Normally, cross-forest group membership is managed by creating shadow groups or by using Universal Groups if both forests are in the same Active Directory environment and have a trust relationship. However, these solutions don't natively support the 'memberOf' LDAP attribute required for LDAP applications.
- For traditional cross-forest group assignment, you might consider the following approaches:
- Group Scope and Group Nesting:Utilize Universal Groups or Domain Local Groups and add users from Forest A to these groups in Forest B. Ensure that Forest Trust is correctly configured.
- Shadow Groups:Mirror the group memberships manually or through scripts/automations to maintain consistency across forests.
- Directory Synchronization Tools:Tools like Microsoft Identity Manager (MIM) or third-party solutions can assist in synchronizing group memberships across forests.
- Partitions and crossRef Objects:
- CrossRef objects (cross-reference objects) in Active Directory are typically used by the Global Catalog and refer to naming contexts or partitions within a forest.
- When dealing with cross-forest scenarios, these crossRef objects do not directly refer to external forest objects. Instead, the trust relationship and associated mechanisms handle cross-forest referrals and forest-wide resources.
- You won't usually create crossRef objects manually for external forests. Instead, you should rely on the trust relationship mechanism that is already in place.
- The 'Partitions' container in Active Directory holds information about all naming contexts in the forest. This includes domain, configuration, and schema partitions but not external forest objects directly.
In summary, while direct usage of crossRef objects for cross-domain group memberships is not a supported method, you should leverage cross-forest trusts, group scopes, and potential directory synchronization tools to achieve your goal. Consider using Universal Groups for cross-forest memberships and ensure that your LDAP applications are aware of the group membership data appropriately.