Add support for mellon auth

[bp85]

• Add proxy_server configuration option for ood_portal.yml
• Install apache packages required for mellon
• creates a script to generate metadata and certs
• Add mellon configs

[bp85]

@treydock I've been using this in prod for well over an year, finally got around to push it upstream.

[treydock]

Suggested change

	MELLON_DIR="<%= scope['apache::params::httpd_dir'] -%>/mellon"
	MELLON_DIR="<%= scope['apache::httpd_dir'] -%>/mellon"

Ensure use correct value is someone overrides

[treydock]

Also the defaults seem to have hardcoded paths while here it's based on Apache data. I think it would be best to define something like openondemand::mellon_dir and make that used as base directory for all these files and paths.

[treydock]

@bp85 Generally I don't recommend deploying things that require manual steps, that somewhat defeats the purpose of Puppet. I think one way to achieve full automation is this:

exec { '/usr/local/bin/mellon_ood_metadata.sh':
  creates => [
    "${apache::httpd_dir}/mellon/mellon.cert",
    "${apache::httpd_dir}/mellon/mellon.key",
    "${apache::httpd_dir}/mellon/mellon_metadata.xml",
  ],
  require => File['/usr/local/bin/mellon_ood_metadata.sh'],
  notify   => Class['apache::service'],
}

[treydock]

I also see some hardcoded paths for Mellon defaults while other places use variables from Apache module. I think all paths should be defined in init.pp , and referenced downstream in various places using maybe the mellon_merged_config variable. This helps ensure if someone changes a variable, for example in this module or Apache module, the things using that path will also reflect that change.