https://answers.axonivy.com/questions/4320/why-has-the-license-check-changed-for-axon-ivy-8-0<p>Why has the license check changed for Axon.ivy 8.0? You need now the so called <a href="https://developer.axonivy.com/doc/latest/engine-guide/installation/index.html#installing-a-licence">public urls</a> and not the hostname anymore. What is the reason why you have changed that?</p>enWed, 15 Jan 2020 05:56:58 -0500https://answers.axonivy.com/questions/4320/why-has-the-license-check-changed-for-axon-ivy-8-0#4322<p>but the 'public url' most not be a registered public domain. It can also be an internal DNS name which workflow users use to access the axon.ivy engine.</p>Reguel WermelingerWed, 15 Jan 2020 05:56:58 -0500https://answers.axonivy.com/questions/4320/why-has-the-license-check-changed-for-axon-ivy-8-0#4322https://answers.axonivy.com/questions/4320/why-has-the-license-check-changed-for-axon-ivy-8-0/4321<p>The driving force behind this is containerisation (e.g. dockers, kubernetes). In these technologies you can easily define the hostname for a specific container. This has made license verification <strong>powerless</strong>.</p> <p>With the so-called <strong>public urls</strong> we can now also ensure license verification in container environments. In order to have only one type of license check, the <strong>public urls</strong> are also used for traditional environments.</p>Alex SuterWed, 15 Jan 2020 04:10:40 -0500https://answers.axonivy.com/questions/4320/why-has-the-license-check-changed-for-axon-ivy-8-0/4321