Skip to main content

License control implementation

This page explains how Vico OpenESB Enterprise edition license control implementation works.

Licenses control is based on Json Web Token (JWT) signed using RSA Private key and verified using RSA Public Key.

License validation is implemented into BPEL Engine component, so if this component is not able to load a valid license file it won't start. All other components do not require any license.

License Content​

OEE Vico license a content is a a JWT with the following content

Header: Algorithm $ Token Type

<![CDATA[{
  "alg": "HS256",
  "typ": "JWT"
}]]>

Payoad: License Information

<![CDATA[{
  "sub": "192.168.18.2",
  "aud": "OEE-Platinium",
  "nbf": 1665671367,
  "iss": "https://vico.org/",
  "exp": 1725141600,
  "iat": 1665671367
}]]>

Payload fields are:

  • sub: IP of the machine where license will be deployed. It is the IP address of the network interface user to access public internet resources. License validation does not require internet access, but yes an IP configured to access internet.

  • "aud": "OEE-Platinium", fixed.

  • "nbf": Time stamp indicating license period beginning

  • "iss": "https://vico.org/", fixed.

  • "exp": Time stamp indicating license period ending

  • "iat": When license was issued

License File Name and Location​

License file name: oee-vico.lic

License mandatory location: OE-Instance/server/jbi/components/sun-bpel-engine/install_root

License Deployment​

License validation is done just when sun-bpel-enginecomponent starts, it is NOTvalidated on component installation neither during component execution. So license validation deployment could be:

  • On a new OEE instance:

    • install sun-bpel-engine component

    • Do NOT start it !!

    • Copy license file

  • Update existing OEE License

    • Replace existing license by the new one.