cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Occasional contributor

In "node-locked" mode - How to deal with the "stolen Labtop" case ?

Jump to solution

In "node-locked" mode, if a user loose his Labtop or had his Labtop stolen, how can I be sure that the LabTop can not use any more ?

Is there a solution in this case ?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Revenera Moderator Revenera Moderator
Revenera Moderator

Re: In "node-locked" mode - How to deal with the "stolen Labtop" case ?

Jump to solution

When a license is fulfilled / generated from a back-office (FNO, LLS or CLS) and if it is persisted to disk (typical instead of processed only into memory), it's immutable. 

Operationally (if the back-office is LLS or CLS), the license model policies can be configured for a more security conscious stance .

For example, configuring a borrow-interval that requires the endpoint to communicate periodically to update / "refresh" its license rights similar to time to live behavior that is separate from the final license expiry. 

View solution in original post

1 Reply
Highlighted
Revenera Moderator Revenera Moderator
Revenera Moderator

Re: In "node-locked" mode - How to deal with the "stolen Labtop" case ?

Jump to solution

When a license is fulfilled / generated from a back-office (FNO, LLS or CLS) and if it is persisted to disk (typical instead of processed only into memory), it's immutable. 

Operationally (if the back-office is LLS or CLS), the license model policies can be configured for a more security conscious stance .

For example, configuring a borrow-interval that requires the endpoint to communicate periodically to update / "refresh" its license rights similar to time to live behavior that is separate from the final license expiry. 

View solution in original post