cancel
Showing results for 
Search instead for 
Did you mean: 

MSMP provisioning to portal via business role fails, but succeeds without business role.

santosh_krishnan2
Participant
0 Kudos

Hi there,

This is an interesting issue so I've debugged it and haven't been able to find a solution.  Below is a snippet from the debug log.  I'll elaborate on the issue further below.

/*********************/20150902185005.6945480:APPL:531:GRAC_WF_REQUEST:New User:********************* created in System(s): *********************

/*********************/20150902185005.6945480:APPL:251:GRAC_WF_REQUEST:Could not update user Attribute "lastname" on name

/*********************/20150902185005.6945480:APPL:000::Could not update user Attribute "lastname" on namespace "com.sap.security.core.usermanagement" of principal "USER.CORP_LDAP.*********************"

The workflow setup has business roles.  The business roles have regular ABAP single roles as well as portal roles in them. 

When portal roles are requested individually, they get provisioned.  But when the same portal role is requested via a business role, we get the above error.

It appears that the request is trying to update lastname back up to LDAP, which isn't what we want.

Has anyone seen this issue? 

Thanks,

Santosh

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member193066
Active Contributor
0 Kudos

Hello,

Could you please paste the mapping of Business role landscape?

Regards,

Prasant