Feature #21605
closed
Make authentication extendable
Added by Marek Hulán about 7 years ago.
Updated over 5 years ago.
Description
Plugins can't easily extend authentications with their own means of authentication if SSL is used. The reason is that #authorize_with_ssl_client before block would always fail on SSL if no client is available. In REX there are use cases where REX core worker is authenticated differently (looking at serial number or using token). The authentication methods should not run if other authentication method already succeeded. That will also help to avoid running both trusted hosts and ssl auth methods that are built in proxy.
- Blocks Bug #17249: All in one setup does not work with regular SSL cert based auth added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/550 added
- Status changed from Ready For Testing to New
- Triaged changed from No to Yes
- Pull request deleted (
https://github.com/theforeman/smart-proxy/pull/550)
- Related to Bug #25001: CVE-2018-14643 rubygem-smart_proxy_dynflow: Authentication bypass in Foreman remote execution feature added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/639 added
- Fixed in Releases 1.22.0 added
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/smart-proxy/pull/641 added
Also available in: Atom
PDF