Re: Web Application authentication

Thu, 14 Sep 2006 21:33:51 -0700

First post!
 
Okay, what about this:
Make a key file on the client server with an expiration date encoded in the key.
Have your program check the key's expiration date every time it runs
When the key expires, call a page on your site to get a new key with a new expiration date.
That way, their site only calls yours once a month. Just don't make the key encoding obvious!
 
Eric

 
On 9/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

No I am not Zend Guarding it.  But the people that I am installing this
application for don't understand HTML much less PHP and CakePHP at
that.  It is just that I need some method to ensure that they don't
change passwords to their FTP server on me and stop paying and are
allowed to keep using the program.  Hard to make a product to compete
in a market that has hosted pay by month solutions if I don't offer pay
by month solution as well.

So, I realy like the authentication since if they removed it it won't
work, but I think for my case maybe the lysine deficiency is best.

Any more thoughts?  AD7Six?  Nate?



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to