GeoffreyMH wrote
Hi there
I have developed an encrypted license scheme for my modules that uses the Portal GUID so I can license them on a Portla by Portal basis.
My question is a simple one, where is the best/recommended place to get Portal Administrators to upload the license to? Of course, if I use the .lic file extension they'd have to have host permissions to upload the file, but since it's encrypted it could just as well be a .txt file. They could upload it to the portal root but maybe there is a better, more suitable place to save licenses already available that I haven't found out about, yet?
And while we are on the subject is there an easy way to specify the file path to the portal root (or the recommended location - it has to be portal specific so that license software for different portals using the same module can know where to find their license).
Now the Portal GUID is exposed, I can't be the only one trying this. So all thoughts would be much appreciated.
Kind regards
Geoffrey
I would suggest using more than just the portal guid. It's nice to have the Portal and Host Guid, but you may want to consider using an additional value.
I have to agree with Mitchell on how you manage your license file. A last resort would be for your customer to have to upload a file through FTP or file manager. Let your module create the file. I would suggest storing the file in the Portals/PortalId folder or in DesktopModules/MyModule directory. There are advantages and disadvantages to both locations. Also, I would suggest using a .config extension for your license. If you use an extension such as .txt. or .xml then anyone will be able to download the license file.
Personally, I prefer to keep all of our module files within our own module directory. You could still manage your portal specific licenses. Create a sub folder under your module directory and store each license file with the associated portalid. We don't need third-party modules storing all over the DNN file structure.
Also, be prepared for increased support requests. Module license protection is still very new to the DotNetNuke Community.
Will