Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-2357

Rename CLI auth extension to follow naming conventions

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: SERVER 6.0.z
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide
      • the CA CLI OID can be referenced either with pp_cli_auth or pp_auth_ca_cli
      • PE's management of this auth.conf setting is updated to use the new name
      • puppetserver's default auth.conf is updated to use the new name
      Show
      the CA CLI OID can be referenced either with pp_cli_auth or pp_auth_ca_cli PE's management of this auth.conf setting is updated to use the new name puppetserver's default auth.conf is updated to use the new name
    • Team:
      Froyo
    • QA Risk Assessment:
      Needs Assessment

      Description

      We recently added a special auth extension to the puppet master's cert, which enables access to the certificate_status endpoints for signing and revoking certs. This extension is currently referenced in auth.conf as pp_cli_auth, but we want to establish a convention of prefixing all auth extensions with pp_auth*. We should add an alias to the extension with the correct prefix and only document that version, to encourage users to expect that naming convention.

      Because we have already shipped some auth.conf files with the old name, in both FOSS and PE, it is necessary for the time being to still allow puppetserver to recognize the old name. Eventually the old version should be removed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                maggie Maggie Dreyer
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support