Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1826

Expose Signing Service public-keys on the UI

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      As a regular user of Automation Hub I can go to some web  page and download the public keys needed to verify the content I am installing.

      Show
      As a regular user of Automation Hub I can go to some web  page and download the public keys needed to verify the content I am installing.
    • ANSTRAT-411 - Content Signing

      On /pulp/api/v3/signing-services/ URL it is exposed all the public keys for a SigningService.

      We need to add to the UI somewhere (call to the UX team) a place where end users can go to download those public keys.

      That interface must show a table like interface with:

      • name of the signing service,
      • the key fingerprint,
      • the text of the public key and
      • a button to download the key as a file
      • The `pulp_created` formatted data

       

       

      $ http :24817/pulp/api/v3/signing-services/
      
      {
          "count": 1,
          "next": null,
          "previous": null,
          "results": [
              {
                  "name": "sign-metadata",
                  "pubkey_fingerprint": "19CD52BD1CA9A00DF10A842D74B14E3590C2231F",
                  "public_key": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n\n [...] \n-----END PGP PUBLIC KEY BLOCK-----\n",
                  "pulp_created": "2020-11-06T15:42:20.645197Z",
                  "pulp_href": "/pulp/api/v3/signing-services/ffb9e987-952f-47e3-a274-ffe69a80ded7/",
                  "script": "/var/lib/pulp/sign-metadata.sh"
              }
          ]
      }

       

              mhradil-1 Martin Hradil
              rochacbruno@redhat.com Bruno Rocha
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: