You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking to automate all use cases of fscrypt for our customer. One of the scenarios we need to account for is key rotation of the protector key. The commands to add and remove protector keys both require the policy ID and the protector ID. In order for us to satisfy the request for everything being automated, we would need a command to fetch these IDs. Currently our only option for a workaround would be to parse the response returned from "fscrypt status", however this isn't best practice.
The text was updated successfully, but these errors were encountered:
We are looking to automate all use cases of fscrypt for our customer. One of the scenarios we need to account for is key rotation of the protector key. The commands to add and remove protector keys both require the policy ID and the protector ID. In order for us to satisfy the request for everything being automated, we would need a command to fetch these IDs. Currently our only option for a workaround would be to parse the response returned from "fscrypt status", however this isn't best practice.
The text was updated successfully, but these errors were encountered: