UME attributemapping for R/3 datasource

[Former Member]

Hello,

The class 'com.sap.security.core.persistence.datasource.imp.R3Persistence' is used in my UME configuration to read user data from an SAP system.

I've noticed that this Java class is calling BAPI_USER_GETDATA which returns all of the user masterdata.

Now, I want to adapt the attribute mappings because some fields available in R/3 su01 (user masterdata) are not populated in the UME (eg. accnt from structure logondata)

Can I extend the default configuration with additional attributes and how is the mapping between the datasource (R/3 user masterdata) and the UME done?

Many thanks,

Danny

[Former Member]

Hello,

The class 'com.sap.security.core.persistence.datasource.imp.R3Persistence' is used in my UME configuration to read user data from an SAP system.

I've noticed that this Java class is calling BAPI_USER_GETDATA which returns all of the user masterdata.

Now, I want to adapt the attribute mappings because some fields available in R/3 su01 (user masterdata) are not populated in the UME (eg. accnt from structure logondata)

Can I extend the default configuration with additional attributes and how is the mapping between the datasource (R/3 user masterdata) and the UME done?

Many thanks,

Danny

[Former Member]

Hello Danny,

The UME attributes mapping is defined in the UME data source descriptor file configured under UME property ume.persistence.data_source_configuration. The file itself is stored in Configuration Adapter -> cluster_data -> server -> persistent -> com.sap.security.core.ume.service. The R/3 descriptor does not allow extension of attribute list (unlike LDAP descriptors where mapping section is presented).

Kind regards,

Tsvetomir

[danny_deroovere]

Thx for your reply Tsvetomir.

I was already afraid that this was not possible. I wounder why it is possible with LDAP and not R/3?

Anyhow, I will have to execute a 2nd BAPI call to retrieve all missing user data.

Thank you for your help,

Danny