User Administration and Authentication

User Mapping

As a prerequisite, all users of the back-end systems that are involved in collaboration processes with SAP Jam must also exist in the SAP Jam system. For SAP Fiori apps, this means all users of both the front-end and the back-end server. This implies an initial load as well as delta synchronization as described in the SAP Jam Administration Guide.

All requests directed to SAP Jam are user-centric. While user data is not explicitly synchronized, user mapping is carried out to link users in the SAP back end and members in SAP Jam. More specifically, as an SAP Jam member is identified by way of an email address, this information must be maintained in the corresponding user profile in the SAP back-end system.

The ABAP SMI API maps the SAP user to the SAP Jam user. This mapping is represented by the Business Add-In (BAdI) BAdI: E-Mail Address for Back-End User (STW_USER_EMAIL_BADI). The default implementation (fallback class) of this BAdI is based on the standard SAP Identity Services. In case of any deviation, this default must be replaced by a system-specific BAdI implementation.