Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-9083

apache : Cannot add flag into SSLCARevocationCheck

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: apache
    • Labels:
      None
    • Template:
      MODULES Bug Template
    • Acceptance Criteria:
      Hide

      While using the flag no_crl_for_cert_ok:

      -> apache configuration vérification succeed

      -> leaf and no_crl_for_cert_ok are considered as two separate arguments

      Show
      While using the flag no_crl_for_cert_ok: -> apache configuration vérification succeed -> leaf and no_crl_for_cert_ok are considered as two separate arguments
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 4.1.0
      Puppet Version: 5.3.7
      OS Name/Version: Ubuntu 16.04

      My goal is to add the flag no_crl_for_cert_ok  in the apache directive SSLCARevocationCheck, as offered in apache documentation.
      Thus, in my puppet module, I use the option ssl_crl_check:

      apache::vhost { 'host':
          [...]
          ssl_crl_check   => 'leaf no_crl_for_cert_ok',
          [...]
      }
      

      Desired Behavior: I expect this directive in the virtual host configuration file:

      SSLCARevocationCheck    leaf no_crl_for_cert_ok
      

      or

      SSLCARevocationCheck    "leaf" "no_crl_for_cert_ok"
      

      Actual Behavior: Unfortunately, I get my sentence surrounded by double quotes:

          SSLCARevocationCheck    "leaf no_crl_for_cert_ok"
      

      Hence, the apache server considers it as a single word and crash upon configuration verification.

        Attachments

          Activity

            People

            Assignee:
            jng JN
            Reporter:
            jng JN
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support