web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Selling Apps (Managed ...
Microsoft Dynamics CRM (Archived)

Selling Apps (Managed Solutions) How do you enforce Licencing?

(0) ShareShare
ReportReport
Posted on by Read 55

Hi

I have developed a (managed) solution that provides business value. I don't have any plugins or complex logic, just entities with forms and a relational structure.

If I wanted to sell this on the marketplace, how can I enforce a licence?

I could create a mechanism for licencing based on:

  • a RSACryptoServiceProvider or similar using the Organisation, dates, a public key, a signature etc, doing a comparison on hash/key values.
  • some external webService to check licencing, called out from a plugin.

But what would stop somebody deactivating my plugin steps so they have no check on Create/Update?

Without plugins/workflows doing any logic (CRUD/business logic) there really is nothing to "turn off" or restrict.

Is anyone aware of any information/links/advice to allow me to licence a managed solution and include a required Trial period?

Thanks

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    ScottDurow Profile Picture
    ScottDurow 21 on at

    If you need to stop people using your entity forms without a license plugin firing you will need to add some JavaScript into the form that queries an entity which has the plugin registered - if the plugin is deactivated then the response will not be as expected and so you can disable or close the window.

    Hope this helps

  • Read Profile Picture
    Read 55 on at

    Thanks for your response, Scott.

    I get that by setting the isCustomizable attribute to false this will kind of lock the JS Webresource down but doesn't this still leave a hole whereby a sysadmin/customizer can turn off (or maybe circumvent) the JS function that does the checking?

    I'm currently investigating using alternate keys in conjunction with some 'licencing' entities/plugins/resources. Maybe without certain (encrypted/decrypted) attributes being present I can prevent CRUD operations?

  • Read Profile Picture
    Read 55 on at

    I'm going to mark this as the answer, Scott as it's more or less where I am with it now. Thanks for taking the time to provide a response, much appreciated.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans