PROBLEM DESCRIPTION: Unable to modify dn value via tacmdedituserVERSION: ITM 6.2.0 FP01When executing the following command, errors occur:tacmd edituser -s localhost -i z727f32 -dnuid=z727f32,o=itmuasentryKUICEU001I Validating user credentials.KUICEU017E The editUser command failed because the valuespecified for - dn -distname option is incorrect.The value for distinguished name is incorrect. Please specify aproper distinguished name or leave the field blank. Verify thatthe correct distinguished name is specified and run the editUsercommand again.However, one can set the correct distinguished name using theGUI. Also noteworthy: if set the uid to o=itmuasentry usingthe GUI, thenit can be set back to O=DEFAULTWIMITMBASEDREALM using the tacmdcommand.
What steps will reproduce the problem? 1:.Fix the compatibility of the D3D11 Plugin (Mudpvr.dll). What is the expected output? What do you see instead? The expected output is:.Play games with the latest graphics improvements of Microso.
So the user and the command appear to be functioningcorrectly, but the check on validity of the user's new settingscannot be done when an external ldap repository is beingreferenced.Confirmation that current behavoir is to only accept default dnO=DEFAULTWIMITMBASEDREALM.Local fixProblem summary. Executing the following command to modify the distinguished nameuser property results in error KUICEU017E:tacmd edituser -s localhost -i z727f32 -dnuid=z727f32,o=itmuasentryKUICEU001I Validating user credentials.KUICEU017E The editUser command failed because the valuespecified for - dn -distname option is incorrect.The value for distinguished name is incorrect. Please specify aproper distinguished name or leave the field blank. Verify thatthe correct distinguished name is specified and run the editUsercommand again.However, one can set the correct distinguished name using theportal client.Also, if setting the UID to o=itmuasentry using the portalclient, then it can be set back to O=DEFAULTWIMITMBASEDREALMusing the tacmd command. So the user and the command appear tobe functioning correctly, but the check on validity of theuser's new settings cannot be done when an external LDAPrepository is being referenced.Problem conclusion.