Skip to content

Using PrivateKeyFiles parameter in oidc_settings causes unrecognized key error #2567

Closed
@uoe-pjackson

Description

@uoe-pjackson

Describe the Bug

When specifying PrivateKeyFiles parameter for oidc_settings puppet fails with

Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Apache::Vhost[example.com]: parameter 'oidc_settings' unrecognized key 'PrivateKeyFiles'

It appears that PrivateKeyFiles is missing from the definition of Apache::OIDCSettings, so should be a case of just adding it.

Expected Behaviour

Successful application of the puppet catalog

Steps to Reproduce

Steps to reproduce the behaviour:

  1. Use the following vhost manifest
apache::vhost { "example.com":
    port              => 80,
    auth_oidc         => true,
    oidc_settings     => {
      'ProviderMetadataURL'       => $oidc_provider_metadata_url,
      'Scope'                     => $oidc_scope,
      'RemoteUserClaim'           => $oidc_remote_user_claim,
      'ClientID'                  => $oidc_client_id,
      'CryptoPassphrase'          => $oidc_crypto_passphrase,
      'PrivateKeyFiles'           => "/etc/pki/tls/private/${siapp_url}-selfsigned.key",
      'PublicKeyFiles'            => "/etc/pki/tls/certs/${siapp_url}-selfsigned.crt",
      'ProviderTokenEndpointAuth' => 'private_key_jwt',
      'RedirectURI'               => '/oidc/redirect',
    }
  }

Environment

  • Puppet: 7
  • Apache Forge: 12.1.0
  • Rocky Linux 8

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions