[FX.php List] FM accts vs. acct & password fields?

[Bob Patin]

I can't imagine letting a web app create FileMaker usernames/ 
passwords... in a small-use situation it wouldn't be a problem, but  
with a situation where there would be hundreds of users, I prefer to  
write them to a table. Using the PHP crypt() function that Chris  
mentioned removes the security issue of having exposed passwords; I  
have a password-retrieval routine that I use with all my web apps, so  
if someone should forget their password I simply write a random  
password to their record, send it to them in an email, along with a  
link that they can click to reset their password very easily.

Bob Patin
Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: tech at longtermsolutions.com
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting

On Jun 19, 2008, at 5:18 PM, Troy Meyers wrote:

> Chris,
>
> I second that. It's great. The only complication is that for  
> password recovery you need to make the user go through some hoops to  
> create a new one, since you have no way of telling them the old one.
>
> -Troy
>
>
>> Not necessarily the case.  If you use PHP's crypt function
>> (http://us.php.net/manual/en/function.crypt.php  ) on the password
>> before storing it in FileMaker, you've stored a   value which can be
>> checked against, but cannot be viewed.  Have a look   at the  
>> function;
>> very cool stuff.
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list