Feature #8748
closed
Allow per-plugin enablement of HTTP in configuration files
Added by Stephen Benjamin almost 10 years ago.
Updated over 6 years ago.
Description
For example, one may want to only enable unauthenticated access to the templates plugin, while still restricting the rest of the plugins to SSL.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/241 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Assignee set to Greg Sutcliffe
- Translation missing: en.field_release set to 28
- Related to Bug #8990: foreman_proxy puppet module should be aware of new plugin http/https settings added
Also available in: Atom
PDF