With external trust it is now possible to establish trust to a subdomain of already trusted forest. This means that for trust to example.com and external trust to child.example.com there are now two trusted paths to reach child.example.com: through forest root example.com and directly via external trust path child.example.com.
This configuration may cause issues when debugging trust-related problems. We need to use shortest path between trusted domains. This means child.example.com should be removed from the list of subdomains of example.com and instantiated as an external trust. This, however, will lead to both child.example.com and example.com be marked with the same list of UPN suffixes because child.example.com UPN list is derived from its own forest root (example.com). Such combination may break UPN support in SSSD.
A solution needs to be developed for covering both trust path and UPN suffix overlap.
What would be a benefit of allowing the overlap?
Should we just prevent this from happening and not allow creating an external trust with a domain in a trusted forest and also prevent establishing a forest trust if one of the domains in the forest is mentioned in the external trust?
I suggest we document for now that it is not supported/recommended and then just make sure the overlap does not happen.
Documenting the limitation is a possibility.
There is no benefit in the overlap other than it seems that AD does not prevent it either.
Metadata Update from @abbra: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5
Metadata Update from @mbasti: - Issue close_status updated to: None - Issue set to the milestone: FreeIPA 4.5.1 (was: FreeIPA 4.5)
Metadata Update from @pvoborni: - Issue set to the milestone: FreeIPA 4.7 (was: FreeIPA 4.5.1)
Metadata Update from @rcritten: - Issue set to the milestone: FreeIPA 4.7.1 (was: FreeIPA 4.7)
FreeIPA 4.7 has been released, moving to FreeIPA 4.7.1 milestone