Expiring license keys lock you out out of the k2management/the update process is too heavy
This is so frustrating. When license keys expire, we are forced to run the configure process, which a) takes quite a bit of time b) occasionally modifies our configuration files since we have custom authentication in place (custom configuration) c) we are used to managing ALL aspects of K2 Management through the browser d) depending on the version of K2, sometimes we will be prompted to update IIS, .Net core libraries This seems completely unnecessary. The license key update should be a very straightforward and easy operation. In the current state of the process, our team does not want to touch this process unless forced to do so. This annoyance makes K2 a lot less competitive through the lack of flexibility.
