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

Grant list repeats itself 4 times when license is read for import #7

Open
eparovyshnaya opened this issue Aug 17, 2022 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@eparovyshnaya
Copy link

Import a license to a product protected with Passage 2.3.0. The offered license will be read its grants exposed for observation prior actual import.
During the exposure you wee list of available grants repeated 4 times.

It does not hurt any further activity, but looks strange and definitely means some internal misbehaviour.

@eparovyshnaya eparovyshnaya self-assigned this Aug 17, 2022
@eparovyshnaya eparovyshnaya added the bug Something isn't working label Nov 23, 2022
@eparovyshnaya eparovyshnaya added this to the 2.3.3 milestone Nov 23, 2022
@eparovyshnaya
Copy link
Author

eparovyshnaya commented Nov 30, 2022

Cannot be repeated on regular licenses.

Possible scenario is the following.
Have a license plan of older formats, like prior 2.0.0.
Then open it in modern Cordon version for any reason.

In order for LCO to operate over an old version of license plan, emf migration is invoked.
It looks like it successfully migrates old-fashion grants to new format, but does not delete old ones.
Thus, next opening will repeat the cycle: old grants migrated to one more porsion of ones of new format, and again are not deleted.
When later you use the license plan for license issuing, it indeed will convert each grant to a personal feature grant of the license under issuing. Thus you phisically can get several copies of the same grant encoded in your license. Which you further can see in License Import Dialog.

License Plan migration can be fixed, test coverage must be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant