Custom logon module : updated UME attribute not available in SAPLogon ticket in first logon

[Amey-Mogare]

Hello,

I have created a custom logon module 'SetIdMappingLogin' to set UME attribute 'REFERENCE_SYSTEM_USER’ for a user if not already set so that user is able to access SAP R/3 applications without any issues.

I noticed that for a user: -

1. When logon module runs, it is able to set this attribute in UME but when user tries to access SAP applications (WD ABAP, BSP iViews) , SSO fails.

2. Now when user logs off and logs in again, SSO takes place with SAP applications.

I am trying to understand why this is happening.

What I think is that the first time, when logon module sets the REFERENCE_SYSTEM_USER attribute for user, this value is somehow not present in MYSAPSSO2 cookie, due to which, SSO fails.

Then 2nd time, attribute REFERENCE_SYSTEM_USER is already 'set', hence logon module does nothing and then, this value is present in MYSAPSSO2 cookie and SSO takes place fine.

Please find attached screenshot for list of logon module I have inside component 'ticket'.

Please help.

Thanks & Regards,

Amey

[Amey-Mogare · Accepted solution]

This is solved by doing below: -

1. Put "SetIdMappingLogin" module just below EvaluateTicketLogin module

2. Make "SetIdMappingLogin" module 'REQUIRED'