Licensing on enterprise application [closed] - licensing

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am developing an enterprise application including central database, MVC web app, Mobile app client, web services and WPF client Windows service application which are working all together, I am going to make a contract with a company to grant them exclusive re-seller Representation .
So I am thinking a way to control the number of sales and provide them a license key for each sale to they could use the key in installation or other step and I want to get informed by the application whenever it is installing somewhere and want to prevent working when the license is used once or is expired or something. I need a solution from people who have same successful experience in this matter, indeed I have some ideas but actually I am not experienced in this issue and I'll be so happy to hear good approaches on this.
Thanks in advance ...

First you need to choose your preferred licensing system. A small list is available in the Question about OS Licensing Components. Second you'll need some kind of service where your reseller can issue licenses without real access to your private license key. E.g. some kind of webservice.
Then you'll have the number of licenses that your reseller has created and you can bill him.
If you also want to know which licenses was activated you can implement some kind of "phone home" in your application.

Related

Should I Store User Data Locally Or Server Side DB? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm working on a 'mental wellness' app, functionality for which includes things such as making journal entries (typed and voice recorded), recording affirmations, creating to-do lists, setting goals/targets etc.
My question is, should I store the user data from the above such actions locally, which gives the user a greater sense of control over their privacy or should I store it on our server in an encrypted DB?
My initial instinct was to go both to allow users to use to do things such as make journal entries even without internet connection, which can then send that data to server/DB once online again. But wasn't sure if this was a major drawback in terms of users privacy i.e. their 'private' journal entries being on our server/DB, albeit encrypted and widely used facilities i.e. AWS, Firebase, Azure. The obvious benefit of having it on server side DB is that they can use different devices such as phone and tablet or can have access if they move to a new device e.g. get a new phone.
But then the alternative I thought of was having users data all stored locally on device and then allowing them to sync to their iCloud or Google Drive or having the app auto sync. Is this a good alternative or compromise?
Is there a preformative benefit one way or the other?
I would appreciate your feedback on what you would consider the best route from both a user experience perspective as well as the technical best practice.
Many Thanks

What to consider opensourcing a Google Appengine application [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
We've made this monitoring tool at our company.
It's not in our line of business so we might as well opensource the tool, and maybe someone else likes it as well, maybe they'll contribute.
The tool runs on AppEngine, so there are so the are some paths in the appengine configuration, that might be a good idea to keep hidden. Unless someone else wants to start using our appengine qouta.
Is there a best practice for open-sourcing AppEngine applications?
Does anyone have any experience to share regarding opensourcing appengine sites?
You can get some ideas from excellent gae-init. The way its working in order to avoid exposing sensitive information, is moving it in a stand alone project, you can even use gae-init for that ;)
As part of the model is a Config class which holds all the information as it concerns the service and its dependencies. There are some default values there but it can also be easily customized from a web interface called admin. Have a look.

CPAL Mule licence [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm interested in Mule ESB but I dont understand the licence, could someone explan me the CPAL licence in simple words?
We have a commercial porduct (JavaEE web application) that neads to be integrated with solutions that are hosting in the cliens environment. For example a clienat has a SAP instalation or any other source of data and want to integrate it with our java web application. We woud like to Mule to achive this functionality, does the CPAL licence allow this?
Our application and Mule could be hosting on our internal machinery or at the clients, both ways are possible.
First: I do not know anything about law.
That said, the CPAL license is based on Mozilla Public License, which is less strict than GPL and you can mix license rather freely as long as the code stays open.
CPAL introduces a concept, that if you run your application with CPAL code in it (Mule for instance), as a "Cloud" service, then you will have to give out the code as well. Simply put, if you alter the Mule source code and host it as a cloud service, you will have to give out your modifications.
I really recommend you to talk to a lawyer in your area (which knows the local laws and immaterial laws etc). However, I do know about a few companies that "bundles" Mule CE with commercial products without concern for license issues in a way very similar to your situation.

How do Licensing enforcement mechanisms work for OEMed DLLs, browser plugins, and ActiveX controls? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I can understand how end-user licensing scenarios work - if valid license key/token is present, then the software works, otherwise, it doesn't work.
But in the case of components that are licensed to be embedded as part of a deployed product, such as a library of UI controls and browser plugins/ActiveX, the license key is not delivered to the executing computer. So how is the licensing enforced? What is the approach?
Thanks!
You can still create a license that the OEM will have to pass on to the end user. One issue for these kinds of embedded components is that if they throw an error it can confuse the application they are used in. LEt's say you use a UI control lib in an app; the UI lib requires a valid license. The license binds to some HW characteristics, like most software activation schemes use. The user changes something in the HW and the binding fails, the UI lib throws a license-not-found error, what does the host app do with it? This one reason why many of these components come with no runtime restrictions. At a minimum you need to be able to either suppress error messages or override the defaults in a way that works with the host app.
HTH
John Browne
Wibu-Systems

Creating and checking license numbers [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
To protect software, you can create a validation system which requires users to provide a valid license number (Often 25 letters or digits) which they have to enter with some personal information. This then gets validated (sometimes aby using a validation server, thus requiring online access) and when valid, the user can use the registered version of an application.
Now, simple question: What kinds of solutions are there which would allow developers to implement such a licensing scheme in an easy way into their applications? I could easily create my own solution but I don't want to re-invent the wheel again...
Ezirez Intellilock has a good solution and API to implement it.
Basicly you created a function of (HW ID, Registration Key) and check if it's right.
Intellilock is just a tool to help you lock the software if the license isn't there.

Resources