The User Mapping tab of Login Properties is a pretty useful screen. Well, now I have a new fun fact about the security GUI.
#USER MAPPED PASSWORD#
At any rate, even after our first process has created a memory mapping to the file(CreateFileMapping) when CreateFile is called by subsequent processes, CreateFile is not returning ERROR_USER_MAPPED_FILE. Mostly because there are a lot of different places where security is listed, and sometimes you have to go to multiple places in order to get a feel for the actual permissions. User mapping requires you to communicate user and password information between the portal and back-end system at least once (during the configuration of user. We have not been able to identify what is different about this user's PC. For example - for the attached screen shot, when passing the script the ADMA1 user name & the fogbugzRelease database the output shoul be dbowner. This REMOTEUSER can be an email like and needs to be mapped to a Linux system user like aoakley. We now ran into a case where the behavior is different on a user's PC running Vista Home edition. We have been able to rely on ERROR_USER_MAPPED_FILE being returned when we call CreateFile with the CREATE_ALWAYS option as a way to know that one of our processes has already created a memory mapping(CreateFileMapping) to our file, and thus open and attach to that mapping, instead of creating a new version of the file.
0 kommentar(er)
