How can i use exisitng user data(Id, password) for user mapping

Question

Hi All,
For User mapping , we can import user mapping data for many users from user administration. and for each user
we can maintain mapping data in the standard format.
eg:
[User]
uid=user2
$usermapping$:BCE:user=ext_user2
$usermapping$:BCE:mappedpassword=password
i am clear till this point.
this all works if we know the userid and passowrd on the system 'BCE'.the passwords on the system 'BCE', are encrypted . so there is no chance for me to know the passwords.
so how can i use the existed userid/passowrd on the system 'BCE' for the mapped user and mapped password on the portal while doing usermapping.
Thanks in Advance,
Lakshmi

Answer 1

Hi,
I think this should work.
1. Setup SSO with SAP logon tickets first. How to do this is described many places, e.g. http://help.sap.com/saphelp_nw04/helpdata/en/d3/41c8ecb31d11d5993800508b6b8b11/content.htm
This SSO will not work at first, because the username is different in the back-end system. So what you need to do is to get the back-end username into the ticket (don't need a password because that is done by the SAP logon ticket)
2. Create a portal component which uses the usermanagement API to create a usermapping which only consists of the username and a blank password. You can do this manually I think if you have no reference system defined.
IUserMappingService umap =(IUserMappingService)PortalRuntime.getRuntimeResources().getService(IUserMappingService.KEY);
//this is the currently logged in user. You might another user
IUserContext user = request.getUser();
//Get the existing data (think it can be null)
IUserMappingData userMapping=umap.getMappingData(systemAlias, user);
HashMap map = new HashMap();
                         map.put(IUserMappingService.UMAP_KEY_USER, backEndUserName);
//add blank password               map.put(IUserMappingService.UMAP_KEY_PASSWORD, "");
//store the values                    userMapping.storeLogonData(map);
Voila, this should allow you to do SSO using SAP logon tickets, but with another name that you use against the portal. I am uncertain if this will work if you have multiple usermappings in the sap logon ticket
PS since the sap logon ticket is issued at logon time, you need to relogon to get the changes done by the code
Regards
Dagfinn