Skip to Content

For an overview of User Mapping in Duet Enteprise 1.0, refer to the following post:

User Mapping in Duet Enterprise 1.0

This method of Duet Enterprise User Mapping can be used in the following circumstances:

– No LDAP connection is available in the SAP Netweaver Gateway System of the Duet Enterprise Landscape

– SharePoint and SAP User IDs are different 

– Multiple Aliases are used in the landscape therefore file manipulation can facilitate different entries.

All user mapping steps will be performed in the SAP Netweaver Gateway System of Duet Enterprise.

1)      Create user mapping records in a text file with extension .csv (ASCII)

The first step is to create the file with the correct mapping values for the users you would like mapped.

The fields would need to be in the following format:

“DN (Distinguished name of each user)”,  sAMAccountName (ADS User ID), SAPUserId

A file would look something like this:

UM_6.JPG

*Note:  If you have maintained the SAP UserID in your ADS or want to prepare a file, you can also create it using the CSVDE tool on the ADS ( see http://support.microsoft.com/kb/327620)

For example, at a command prompt type in

csvde -d “CN=Users, DC=Domain” -l “samaccountname,sapusername” -f c:maps.csv

2) Once you have file, you need to add it to as a Logical File Name to the SAP Netweaver Gateway System.

a)  Go to transaction FILE and add a new directory or use one already existing in this transaction. 

UM_1.JPG

b) Add your file to the directory specified (make sure it has an extension of .csv).

c) Go to transaction SF01 and create a new Logical File Name to represent your mapping file.  Include the Logical Path and the physical file name.

UM_2.JPG

 

3)      In the SAP Netweaver Gateway System, specifiy the File for mapping users by navigating to the following path:

         SAP NetWeaver -> Gateway -> Generic Channel -> Configuration -> Consumer Settings -> Select User Mapping Type

um_3.JPG

Enter a new entry for File based user mapping, config index will be the next available number (must be unique from other records), enter the Logical File name definition ( in this case *LF_BULK_USER_MAPPING*).   Make sure to click on the Active flag so that the user mapping program knows to use this method of mapping.  Save the entry.

4) Last step is to Map SAP User Names to Consumer.  Navigate to the same menu as outlined above except choose Map SAP User Names to Consumer.

For a file based mapping, there needs to be at least 3 fields in the file you created separated by a delimiter (we are using comma)

“<DN String>”,<ExternalId>,<SAPID>

The badi used for mapping really only looks at the 2 last fields <ExternalId> and <SAPID> but the first field must be there as a place holder with Quotes.

Populate the following fields:

Client: <SAP Netweaver Gateway Client>

External ID Type: SA

Prefix of External Name: SharePoint::<domain>\

    – if users exist in multiple domains or aliases in your landscape, you could just put in SharePoint:: and then manipulate the file so that the

      externalId has the prefix of the domain directly in the external id.  For example, your file would look like this: 

      “<DN String>”,<domain>\<ExternalId>,<SAPID>

UM_8.JPG

Name of Issuer: Sharepoint Security Token Service

BAdI Implementation: SharePoint Integration bulk user mapping

UM_4.JPG

After your run the program out of test mode, go to transaction se16, enter table USREXTID and you will see your user entries.  If you look at the last field of the record, you will see a guid in field ISSUERH.  This corresponds to the Issuer information you provided when running the mapping. 

UM_7.JPG

Mapping is complete. 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply