When configuring user remapping, you must specify the appropriate prefix with each user in the remapping table. The following examples how you can specify entries in a user remapping table for various scenarios:
To remap inbound changes from the claims-based CORPORATE\susan account to a generic, forms-based support account on the Extranet Portal, we would use the following remapping on the Extranet Portal:
<User OldUser="i:0#.w|CORPORATE\susan" NewUser="i:0#.f|sqlmember|support"/>
Alternatively, if in the previous example, the outbound web application was using classic authentication, then there would not be a token prefix and we could specify the mapping as follows:
<User OldUser="CORPORATE\susan" NewUser="i:0#.f|sqlmember|support"/>
·Metalogix Replicator for SharePoint version 4.1, builds 3375.151 and higher
·Metalogix Replicator for SharePoint version 5.0
Replicator; authentication; Claims-based authentication; Forms-based; CBA; FBA
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center