Hi Eric, thanks for replying!
The problem is that in order to call the Win API to change an user's password I must be logged as an administrator, so... back to same problem :(
Fernando
>Hi Fernando!
>
>Other suggestion would be a dynamic password. It would be based on Date and Time in computer (all like char). Sample: Hour + Day + Min + Month + ... Thus:
>
>1 - Computer Date and Time: 02/15/2004 08:05:01
> Password: 08150502
>2 - Computer Date and Time: 02/15/2004 09:27:01
> Password: 09152702
>
>Of course that you could to combiner of much diferent ways.
>Ops... LoginId isn't necessary in this case, you could to put some login to disguise. 8-D
>
>
>
>>Hi,
>>Reading article Securing VFP Data, by Alf Bormann in FoxTalk's September 2003 issue (requires login to access), learned about a thing that was completelly new to me: "impersonation". Well, that oppened many new opportunities to my VFP app development.
>>
>>In the first app that I'm developing, using impersonation, I have this situation where it will be run by different users (under different logins) but in order for it to perform certain tasks, that require a network administrator login, it will impersonate using the administrator's login id and perform the task.
>>
>>It's all ok in the implementation, it impersonates, performs those tasks, gets back to the original login and so forth.
>>
>>The only problem I'm facing (so far!) is to determine the best way to store (read "hide") the administrator's login and password. Better than that, if I could have a way that *only* the network administrators could set (or store) the login/password and the app could retrieve it for utilization.
>>
>>Some options that came up (and were discarded, maybe too soon <s>):
>>- Hard code it inside the app source code
>> - Store it in an .ini file
>> - Store it in a field of a Dbf Table
>> - Encript it and store it in...
>>
I would be very happy to count on your comments and suggestions, thanks!
>>Fernando
>
