Entering content frame

This graphic is explained in the accompanying text Example: Type-Based Data Partitioning

In type-based data partitioning, principals of different types (users, groups, and so on) are stored on different data sources.

In the following example, all new users are stored on a database, and new groups are stored on the LDAP server. In more detail, this means that:

·        All new users get an ID from the database data source. The unique ID of new users starts with "USER.PRIVATE_DATASOURCE."

·        All new groups get an ID from the LDAP data source. The unique ID of new groups starts with "GRUP.CORP_LDAP."

·        All namespace-attribute-value triples for which the database data source is Structure linkresponsible for are stored on this data source, all others are distributed on other data sources.

·        All namespace-attribute-value triples for which the LDAP data source is Structure linkresponsible for are stored on this data source, all others are distributed on other data sources.

Example

<dataSource id="PRIVATE_DATASOURCE"
        className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
        isReadonly="false"
        isPrimary="true">
    <homeFor>
        <principals>
            <principal type="USER">
            <!-- No substructure specified means home for all principals of type  
                 "USER" except the ones in notHomeFor-Section -->
            </principal>
        </principals>
    </homeFor>
    <notHomeFor>
    </notHomeFor>
    ...
</dataSource>

<dataSource id="CORP_LDAP"
        className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
        isReadonly="false"
        isPrimary="true">
    <homeFor>
        <principals>
            <principal type="GRUP">
            <!-- No substructure specified means home for all principals of type 
                 "GRUP" except the ones in notHomeFor-Section -->
            </principal>
        </principals>
    </homeFor>
    <notHomeFor>
    </notHomeFor>
    ...
</dataSource>

 

 


 

 

Leaving content frame