Eclipse Passage

The Eclipse Passage project aims to provide rich and easily adoptable capabilities to define and control licensing constraints.

The usage story starts in Licensing Operator client:

• Define a product you would like to ship
• Generate a pair of keys for defined product
• Send the public key and product description to your development team
• Discuss the features with your marketing and map the features to the product
• Send the descriptions of the features to your development team

Then development team needs to do the following:

• Embed the public key to your product
• Bind functionality to feature identifiers
• Include Licensing Runtime bundles to the product

Well, you are ready for the product shipment, at least from Passage point of view. After some time you hopefully will have fantastic download rate and a lot of requests to obtain a license, you need to use Licensing Operator client again:

• Register licensee: either user or company
• Formulate the license conditions: allow a set of features for particular node or for some period or whatever you would like
• Encrypt the license file and send it to the user: you will need a product private key for it - but we hope you still have it in some safe place

Finally, the Licensing Runtime is starting its work inside your product deployed to the customer environment using the simple algo:

• Collect the configuration requirements (feature identifiers to be controlled)
• Mine the license conditions using different approach, the default may be to inspect a subfolder @user.home
• Evaluate the mined conditions against current environment state (time now, running node id) to obtain feature permissions tickets
• Put both configuration requirements and feature permission tickets to the examiner to receive verdict (restrictions)
• Call restriction executors to have desired effect: show status bar reminder or block everything

That's it!