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

custom_trusted_oid_mapping does not work

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.3.2
    • Component/s: Puppet Server
    • Labels:
      None
    • CS Priority:
      Reviewed

      Description

      Steps to reproduce:

      Create on master:

      /etc/puppetlabs/puppet/custom_trusted_oid_mapping.yaml

      ---
      oid_mapping:
        1.3.6.1.4.1.34380.1.2.2:
          shortname: 'ap_rs_cloud_id'
          longname: 'RightScale Cloud ID'
        1.3.6.1.4.1.34380.1.2.3:
          shortname: 'ap_rs_account'
          longname: 'RightScale Account'
      

      Check permissions:

      -rw-r--r-- 1 pe-puppet pe-puppet 213 Feb 10 02:47 /etc/puppetlabs/puppet/custom_trusted_oid_mapping.yaml
      

      Restart puppetserver: service pe-puppetserver restart

      On agent create this:

      /etc/puppetlabs/puppet/csr_attributes.yaml

      extension_requests:
        1.3.6.1.4.1.34380.1.2.2:  '8'
        1.3.6.1.4.1.34380.1.2.3:  '77504'
      

      Install Puppet agent from the master using the Curl command

      Add the following to site.pp

      notify { "trusted_hash":
          message => $::trusted['extensions'],
      }
      

      Output on the agent (styled):

      {
        "1.3.6.1.4.1.34380.1.2.2"=>"8", 
        "1.3.6.1.4.1.34380.1.2.3"=>"77504"
      }
      

      Expected output:

      {
        "ap_rs_cloud_id"=>"8", 
        "ap_rs_account"=>"77504"
      }
      

      I have also tried adding trusted_oid_mapping_file to puppet.conf with no luck

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                erik Erik Dasher
                Reporter:
                dylan.ratcliffe Dylan Ratcliffe
                QA Contact:
                Erik Dasher
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support