These examples show you how multiple portals accessing the same user repository can share content. All portals involved in the relationship must import the same users and groups from a single user repository.
There are two scenarios for building a composite portal:
Multiple Content
Portals: Multiple content
portals each possess links to a large number of documents. A single user
can visit the separate content portals, always with the same user name
and password, and always receive access to the correct content.
In this example, each portal acts as both a serving and a requesting
portal.
One Master Portal:
One portal is set up as a master portal rather than a content portal.
Through this master portal, users can access content from the various
content portals.
In this example, the master portal acts as the requesting portal, and
the content portals act as the serving portals.
On each serving portal, the administrator creates an incoming federated search.
On the Main Settings page of the Incoming Federated Search Editor, the administrator includes the authentication sources that the serving portals share with the requesting portal. This way, all users making requests of a serving portal need to be imported into the portal through this common authentication source.
On each requesting portal, the administrator creates an outgoing federated search for each content portal.
On the Main Settings page of the Outgoing Federated Search Editor, the administrator selects No for Send portal authentication. Users will make the requests using their own user accounts.