User Mapping to R/3 - admin.pwdprotection=false but still pwd field appears

Question

<br />
Hello All,<br />
I am doing SSO using user mapping to R/3 system from Portal as the ids are different for Portal and R/3.<br />
I can access a transaction iview from R/3 successfully using user mapping(in SSO) but the problem is everytime a user changes his R/3 password, the mapped password is to be changed in Portal.Otherwise, unable to access transaction iview.<br />
1) I have changed the property ume.usermapping.admin.pwdprotection=false in configtool but still in User Admin > User mapping for system access , the password field is populated and while accessing the R/3, the password is being verified. I have seen in another system where the password field is not being asked after modifying the property to false, only id field is present. From the end user, under Personalize > User Profile > User Mapping for system, no systems are present as expected for mapping. Logon method in system is uidpw and mapping type is "Admin".<br />
Versions - Portal is NW7.0 SP18 and ECC is .0 EhP3.<br />
anybody faced the same problem? Is there a note to fix it?<br />
2)Also, in the User Admin > User mapping for system access , in the dropdown I can see the system aliases I have created in systems but not in System admin> sys config > Ume config > under User Mapping , I do not find any reference system. <br />
After first restart it was not there, after some time it has come, later it was coming as configured but invalid beside the system in braces in dropdown like abc(configured but invalid). Once I unselected, now it is no more available in dropdown.<br />
3) I have used diagtool to identify the problem. In the ticket, how do I see the mapped user?<br />
I am seeing only the following details.From the log - <br />
The created ticket is: <br />
[ [Ticket [initialized]<br />
  Ticket Version  = 0<br />
  Ticket Codepage =  (Encoding=1100)<br />
  User = 121444<br />
  Issuing System ID     = EPD  ( Portal name)<br />
  Issuing System Client = 000<br />
  Creation Time = 200905150649<br />
  Valid Time    = 8 h 0 min<br />
  Signature (length=261 bytes)<br />
  InfoUnit id=32, name=portal_user, content=portal:121444, length=16<br />
  InfoUnit id=136, name=authscheme, content=basicauthentication, length=19<br />
  InfoUnit id=1, length=9<br />
  InfoUnit id=2, length=3<br />
  InfoUnit id=3, length=3<br />
  InfoUnit id=4, length=12<br />
  InfoUnit id=5, length=4<br />
  InfoUnit id=10, length=9<br />
]. <br />
Authentication stack: [ticket].<br />
<br />
Does this have an entry for mapped user of target R/3 system also?<br />
If I am not finding the userid/pwd in ticket, how is SSO working? based on user mapping only?<br />
Thanks,<br />
Isvarya<br />

Answer 1

Thanks Anja for the quick response.
My primary objective is to use SSO with logon tickets to backend which is independent of user passwords.
regarding 1)
From the link -
http://help.sap.com/saphelp_nw70/helpdata/EN/f8/3b514ca29011d5bdeb006094191908/frameset.htm
Features
●      Either users or administrators can perform user mapping.
¡        Users must always enter a password to validate their mapped user ID.
This password is not stored, but is used to confirm that the user is entering a user ID with which he or she has access to the ABAP-based system.
○       Administrators can enter a password to validate their entries.
The UME property ume.usermapping.admin.pwdprotection defines whether or not the administrator must enter a password. By default the administrator must enter one.
is also in the same lines.
But as per the SAP library link, I do not find a reference system  because of problem 2 in the initial post.
Also, I have a screenshot of user admin where the password field itself is not present. If you can share your email id, I will send the scrnshot without pwd and mine with password.
2)I have seen this note. But, none of the 3 cases mentioned are applicable to me..user mapping is working just fine..Only reference system is not populated. 
3) Becuase of 1, I was expecting to see mapped id alone or mapped id along with system name in logon tickets.
Thanks for the response.