Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish activation limit errors between floating and hosting type #33

Open
B3QL opened this issue Nov 10, 2023 · 1 comment
Open

Comments

@B3QL
Copy link

B3QL commented Nov 10, 2023

We support both types of licensing (node/floating) and we want to handle the activation limit error differently depending on the case.
Currently, the client returns the same error (code 58) for both license types.
Furthermore calling the GetLicenseType() raises the Unknown error exception for non-activated licenses
which prevents from obtaining the type.

Is there another way of getting the license type?

@adnan-kamili
Copy link
Contributor

I am not sure we can support it without a breaking change. My suggestion would be to add a prefix/suffix to the floating licenses. This can be automated by updating the "KeyPattern" regex in the license template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants