You can either set a variable when the app ships with an expiry date. I've done this sort of thing before with entry of a serial number (which needs to be validated in some way) then changes the expiry parameters. The other way is to have the file quesry a remote file somewhere and see if it meets certain criteria. Number of users will need to use the second method as it will need to all copies to talk to some point to check how many are using it.
I am curently looking for the same thing and I am testing the ideas from formulations pro
check them out
Actually, there is a little known method of not using the FileMaker's SSL cert, but using a trusted one and making sure it is only particular machine by domain name. This verifies it is not run on another machine. Also, make sure you control the DNS records.
It is best if you control the admin account. But if you do give them full access and they violate controls you setup with your scripts, and if you control the DNS server, then you can just change their A record and their system will quit working.
You'll have to get with FileMaker support to get instructions on how to substitute a trusted cert for the default cert.
Thanks for your reply Taylor.
Seems a good solution.
But I am a newbie here, I know about SSL cert, but I don't know how they can be related to Filemaker database and can be used in identifying devices uniquely.
Can you please come up with some more details?
I like the second method you mentioned, but not sure how it could be implemented.
Thanks Michael for sharing this.
I will also share my owns when I found something.
Currently I am thinking about Gary Tate's Idea to have a remote file for licensing purposes and every solution at client side to be validated from it on each start.
Pixi, I am agree with you.
But removing admin access only limits the access to source.
So if we remove admin account people will not be able to see or change the solution schema but they can use, copy and distribute the working solution unlimitedly.
SSL Certificates tie a machine by IP to a domain through a trusted secure company. FileMaker installs its own certificate on a FileMaker Server service and uses it as part of the secure connection process between the clients (FMP) and the server (FMS). The certificate FileMaker installs is a self generated one and not tied to a secure company. But you can swap out the FileMaker installed one with a secure company issued SSL certificate. You will need to contact FileMaker Support on how to do this.
And for a list of SSL Certificate vendors for FMP: http://help.filemaker.com/app/answers/detail/a_id/11413/kw/ssl%20certificate
Good find. Have you had success implementing the formulationspro solution in your licensed databases?
I've had this in the back of my mind (who doesn't?) for awhile now. Would love to hear more about what you found.
You've got to decide how you want to balance convenience vs security. Having no restrictions on copying is very convenient but not secure. Some expensive software requires registration, activation, and a dongle to be plugged into a machine for the software to run. That's very secure, but very inconvenient.
Even the "big" players like Microsoft and FMI have problems with piracy, but they're aware how the inconvenience of certain measures can lose sales.
Seriously, how many sales do you expect to lose if you have a bare minimum security? I don't mean how often the app will be used unlicensed. That's an important number ( the theoretical max of the sales loss), but some of those people wouldn't buy it anyway, so you haven't lost their sale. Balance that sales loss against a) the time you spend creating and maintaining your security and b) the sales loss from people who dislike the inconvience of your security.
My recommendation is to go minimal. Issue a license key tied to an e-mail address.