# Simplify Notation AKV sign/verify experience Notary v2 Simpler path for [this article](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-build-push) mapping to corresponding steps: ## Install the notation CLI and AKV plugin 1. Install steps --> simpler via install via package manager. a. `choco install notation` b. `apt get notation` and `apt install notation`. After install you `apt get update` Existing work item: https://github.com/notaryproject/notation/issues/204 2. Simpler plugin add experience `notation plugin add azure <plugin file>` Existing work item which you still have to download the file, but it puts it in proper directory: https://github.com/notaryproject/notation/issues/193 What would be a better experience is if the `notation plugin install azure` knows how to automatically download and install the latest notation AKV. This would be a similar experience to [docker plugin](https://docs.docker.com/engine/reference/commandline/plugin/) This is called out in a [comment here](https://github.com/notaryproject/notaryproject/issues/163#issuecomment-1219770500). Alternative approach: get plugin also via package manager similar to #1 ## Configure environment variables 1. Removed. Put into `notation cert generate` command below 2. Move to build and sign container image section. This has nothing to do with notation itself. ## Create a self-signed certificate (Azure CLI) All steps replaced with: ``` notation cert generate --plugin azure --kms <name> ``` Existing issue: https://github.com/notaryproject/notaryproject/issues/163 ## Verify the container image against signatures Additional section needed for trust policy. Yi's proposal: https://hackmd.io/EMkTlPleSQqL-Ej03esL8w#Verify-the-container-image-against-signatures Steps replaced by: `notation policy create` Existing issue: https://github.com/notaryproject/notation/issues/398 ## Build and sign a container image 2. Can we not have `azure login` or a **single** place in the entire document we login/authenticate once? Then this step gets eliminated. 3. Make COSE default signature format and JWS be the one you have to put a parameter for.