ping process + validate-key is changing license update date, causing lastValidated = updated

[codechair]

Not sure if that's intended, a bug on my or your end, but when I run the ping process action, followed by validate-key with a fingerprint, the license's 'updated' date changes. This is causing the license's lastValidated = updated , on every validation, even if we're not really updating the key. Let me know what I'm missing. Many thanks!

[ezekg]

Validating a license will change its updated timestamp because its last validated timestamp also changes. This is expected behavior. Any time an object is changed, the updated timestamp is updated to reflect when that change occurred. Why is this a problem?

[codechair]

Thanks for the quick reply.

Your explanation does make sence to me, but it's not consistent with the api response from the documentation (which led me to think a validation would NOT trigger an update): https://keygen.sh/docs/api/licenses/#licenses-actions-validate-key

The example shows a response where lastValidated > updated. If I understand your logic correctly, it should always be updated >= lastValidated, right?

[ezekg]

It depends. The update sequence is performed out-of-band to the validation cycle, so it may or may not be equal. And concurrent updates from other consumers may also effect this, e.g. if there are multiple machines validating the license, or if an admin is updating the license, or if a background process is updating the license, etc. I wouldn't go in assuming these values will always match.

But yes, generally speaking, the updated timestamp should always be equal to or greater than the last validated timestamp.

Lastly, the example in the docs is for representing the schema, not for making assumptions of real values.