labs64 / netlicensing-gateway

Labs64 NetLicensing / eCommerce gateway

Labs64 NetLicensing / eCommerce Gateway

Use any eCommerce platform, such as FastSpring, MyCommerce, PrestaShop, SendOwl, and many others as a license acquisition frontend. After a successful transaction, all needed licensing configuration (Customers, Licenses and all related data) will be made available in the NetLicensing and can be used for later entitlements validation in NetLicensing.

License Acquisition Flow

How to use this image

There are various ways available on how to enable NetLicensing Gateway in your licensing flow:

• Centrally hosted instance available at gateway.netlicensing.io
• Your individual instance from Docker image (check instructions below and in the contributing instructions)

Docker

Pull official NetLicensing Gateway image

$ docker pull labs64/netlicensing-gateway

Start container

$ docker container run -d -it --publish 8080:8080 --name netlicensing-gateway labs64/netlicensing-gateway

Test configuration

Sanity check

Verify container configuration by opening monitoring endpoint at http://localhost:8080/gateway/monitoring

Connectors tests

Refer to the eCommerce connectors setup and configuration guides.

Contributors

New integrations (eCommerce connectors) as community implementation are highly appreciated and welcome. Please refer to the contributing instructions.

Bugs and Feedback

For bugs, questions and discussions please use the GitHub Issues.

License

NetLicensing Gateway is open-source software licensed under the Apache 2.0 license.

Links

• NetLicensing Gateway Docker image
• NetLicensing Integrations
• NetLicensing RESTful API

netlicensing-gateway's Issues

Enable 2checkout integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation: https://knowledgecenter.2checkout.com/API-Integration/Webhooks/06Instant_Payment_Notification_(IPN)

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Authorize.Net integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • https://developer.authorize.net/api/reference/features/webhooks.html
  • https://github.com/AuthorizeNet

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Gumroad integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • https://gumroad.com/ping

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Chargebee integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation: https://apidocs.chargebee.com/docs/api/events

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable FastSpring integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • https://docs.fastspring.com/products-bundles-and-subscriptions/fulfillments

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Paddle integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation: https://developer.paddle.com/webhook-reference/intro

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Zuora integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • Test Drive: https://www.zuora.com/zuora-test-drive/
  • Callout: https://knowledgecenter.zuora.com/CF_Users_and_Administrators/Notifications/E_Configure_Callout_Notifications
  • Sample Receiver: https://knowledgecenter.zuora.com/CF_Users_and_Administrators/Notifications/F_Sample_Code_for_a_Callout_Receiver

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Verify spring security path

In the spring security configuration https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/resources/context/security.xml#L15
the path mycommerce/keygen points to a non-exisiting endpoint.

• Is there any reason to define such path?
• how the real path is protected then: https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/util/Constants.java#L29

Enable Recurly integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• NetLicening RESTful API: https://netlicensing.io/wiki/restful-api
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation: https://dev.recurly.com/page/webhooks

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• NetLicensing Community Support: https://github.com/Labs64/NetLicensing-Community

Refactor individual integrations in one single package

Current integrations implementation (e.g. MyCommerce) is distributed across several packages, which increases significantly the maintenance effort.
Following need to be considered:

• introduce the foundation (base) gateway classes
• move integration of specific classes in the dedicated package
  • every new implementation should be using the same pattern/structure
• avoid multiple configurations locations while enabling the new integration

Expected: a plug-in approach for enabling the new integrations.

Enable billwerk integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation: https://developer.billwerk.io/Docs/Webhooks

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Security Alerts - org.springframework.data:spring-data-jpa (low severity)

CVE-2019-3797
Vulnerable versions: < 1.11.20
Patched version: 1.11.20

This affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19. Derived queries using any of the predicates ?startingWith?, ?endingWith? or ?containing? could return more results than anticipated when a maliciously crafted query parameter value is supplied. Also, LIKE expressions in manually defined queries could return unexpected results if the parameter values bound did not have escaped reserved characters properly.

---

https://github.com/Labs64/NetLicensing-Gateway/network/alert/pom.xml/org.springframework.data:spring-data-jpa/open

---

Upgrade org.springframework.data:spring-data-jpa to version 1.11.20 or later.

Enable MoonClerk integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • https://github.com/moonclerk/developer/blob/master/integration.md

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable Stripe integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • https://stripe.com/docs/billing/webhooks

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Enable SendOwl integration

Use Case:

Frontend e-commerce systems offer an excellent customer experience by providing Subscription Management, Payment Options, Billing & Accounting, Analytics, Security & Compliance.
ISV will be able to use NetLicensing Gateway integration with the chosen frontend e-commerce system to allow customers to acquire licenses for their products. After license(-s) acquisition, necessary assets will be created and assigned to the customer within NetLicensing system during the fulfilment process.

Typical integration tasks:

• NetLicensing creates and delivers Customer number to be used as an identifier during the shopping process
• E-Commerce system triggers configured NetLicensing Gateway endpoint during the fulfilment process
• NetLicensing creates and assigns Licenses to the current Customer

References:

• Typical e-commerce integration flow: https://github.com/Labs64/NetLicensing-Gateway#license-acquisition-flow
• Sample implementation (MyCommerce): https://github.com/Labs64/NetLicensing-Gateway/blob/master/src/main/java/com/labs64/netlicensing/gateway/controller/restful/MyCommerceController.java
• NetLicening RESTful API: https://www.labs64.de/confluence/x/pwCo
• NetLicensing test account: demo:demo or your own
• E-commerce integration documentation:
  • Licenses list: https://www.sendowl.com/blog/how-to-sell-license-keys.html
  • Web-Hooks (fulfilment): https://help.sendowl.com/help/using-web-hooks

---

Support

Feel free to contact us for support via:

• Email: [email protected]
• Telegram chat: https://t.me/netlicensing

Dockerize NetLicensing Gateway

Enable NetLicensing Gateway to start within Docker container.

Use Cases:

• local development
• on vendor's premises to connect with the third-party e-commerce, ERP and CRM solutions.

java.lang.NoClassDefFoundError: org/glassfish/jersey/internal/inject/AbstractBinder

Runtime exception during controller call.

	java.lang.NoClassDefFoundError: org/glassfish/jersey/internal/inject/AbstractBinder
		at java.lang.ClassLoader.defineClass1(Native Method)
		at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
		at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
		at org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2395)
		at org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:857)
		at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1329)
		at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1182)
		at org.glassfish.jersey.jaxb.internal.JaxbAutoDiscoverable.configure(JaxbAutoDiscoverable.java:58)
		at org.glassfish.jersey.model.internal.CommonConfig.configureAutoDiscoverableProviders(CommonConfig.java:624)
		at org.glassfish.jersey.server.ResourceConfig.configureAutoDiscoverableProviders(ResourceConfig.java:811)
		at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:447)
		at org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:184)
		at org.glassfish.jersey.server.ApplicationHandler$3.call(ApplicationHandler.java:350)
		at org.glassfish.jersey.server.ApplicationHandler$3.call(ApplicationHandler.java:347)
		at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
		at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
		at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:255)
		at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:347)
		at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:392)
		at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:177)
		at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:369)
		at javax.servlet.GenericServlet.init(GenericServlet.java:158)
		at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1144)
		at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
		at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:985)
		at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4885)
		at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5199)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
		at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
		at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
		at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714)
		at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:970)
		at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1841)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.run(FutureTask.java:266)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
		at java.lang.Thread.run(Thread.java:745)
	Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.internal.inject.AbstractBinder
		at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1360)
		at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1182)
		... 38 more