Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 273 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Own module protection
MaW
Member Posts: 74
Hi,
Is there a way to use serial codes or something like that to secure different functionality within a custom module?
We have a small module which we do not want to certify through the CfMD process.
Our module is build up as a module with basic functionality for one price. Various extra functionality is available if the customer buys it, and we activate that with parameters which can be ticked on and off.
We would like to make sure that the extra functionality can only be accessed if the customer has purchased it.
Most ways to do that is easy to for another partner to bypass with small changes in the code. Is there any solution for this, or do we just trust each other as partners?
Thanks.
Is there a way to use serial codes or something like that to secure different functionality within a custom module?
We have a small module which we do not want to certify through the CfMD process.
Our module is build up as a module with basic functionality for one price. Various extra functionality is available if the customer buys it, and we activate that with parameters which can be ticked on and off.
We would like to make sure that the extra functionality can only be accessed if the customer has purchased it.
Most ways to do that is easy to for another partner to bypass with small changes in the code. Is there any solution for this, or do we just trust each other as partners?
Thanks.
0
Comments
"God and developers are in a constant battle. Developments to make their applications more idiot-proof, and God to produce bigger idiots!"
Thanks for the reply. I figured that was the situation.
Better to put the energy into making a good solution, than to use it on trying to secure it.