Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAdding Security To Modules?Adding Security To Modules?
Previous
 
Next
New Post
12/12/2014 11:08 AM
 

Hey all,

I have seen some modules that require the user to enter a serial/registration number upon adding it to a page. Is this the preferred method to lock down a module or are there other ways of doing it?

Can anybody point me in the right direction so I could see the methodology/how to implement this kind of behavior in my own modules?

 
New Post
12/15/2014 5:28 PM
 
there is no one way, most module developers implement their own licensing solutions (often using 3rd party licencing components or free opensource ones such as https://www.codeplex.com/site/search?... )

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
12/16/2014 1:34 PM
 
Some way back, like 2006 or so, I created what was probably the first copy protection mechanism in a DNN module based on assymmetric encryption. I later approached DNN to see if it would be possible to roll something into the installer so we could do this properly. Although there were some half-hearted promises back then, this has never materialized. Nowadays I am in a better position to propose something, so I may well do that. The crux, IMO, is to provide a module "hooks" during the installation process. I.e. some way to take the user through a full licensing experience. Note that this is not just about "activating" a module. I also implement "trial activation" for instance and limited time support and upgrades (which can be renewed). All these aspects need to find a place in one smooth customer experience.

Peter

Peter Donker
Bring2mind http://www.bring2mind.net
Home of the Document Exchange,
the professional document management solution for DNN
 
New Post
12/20/2014 2:22 PM
 
I asked a similar question back in April http://www.dnnsoftware.com/forums/for...

I did some research back then and saved some bookmarks. I haven't tried any of these. Let us know which one worked for you or anyone who used one can post some feedback.  I wish DNN software creates some kind of a licensing api module developers can hook to. I am developing a module and the I have deferred the licensing stuff to the very end. It's the least desirable part and the one that contributes nothing to the feature set. 

http://www.activelocksoftware.com

http://www.eziriz.com/intellilock.htm

http://www.ssware.com/cryptolicensing/features_net.htm

http://www.licensingdotnet.com/pricing.htm

https://github.com/ayende/rhino-licensing

https://installkey.codeplex.com/

https://softwareprotector.codeplex.com/

http://www.codeproject.com/Articles/35009/How-to-Generate-and-Validate-CD-Keys-for-your-Soft

http://www.developer.com/net/csharp/article.php/3074001/Applications-Licensing-using-the-NET-Framework.htm


 

 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAdding Security To Modules?Adding Security To Modules?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out