[SERVER-1732] Set use_legacy_auth_conf to default to false - Puppet Tickets

XML

Word

Printable

Details

Type: Task
Status: Closed
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: SERVER 5.0.0
Component/s: Puppet Server
Labels:
None

Team:
Systems Engineering
Sub-team:
- Server
Story Points:
1
Sprint:
Server 2017-04-05

Release Notes:
Deprecation
Release Notes Summary:

Hide
The default value that Puppet Server uses for the "jruby-puppet.use-legacy-auth-conf" setting, when not specified in the puppetserver.conf file, has changed from "true" to "false". By default, the HOCON-based auth.conf file which uses trapperkeeper-authorization will now be used for evaluating security access to HTTP endpoints instead of the legacy Puppet auth.conf file.

Show
The default value that Puppet Server uses for the "jruby-puppet.use-legacy-auth-conf" setting, when not specified in the puppetserver.conf file, has changed from "true" to "false". By default, the HOCON-based auth.conf file which uses trapperkeeper-authorization will now be used for evaluating security access to HTTP endpoints instead of the legacy Puppet auth.conf file.

QA Risk Assessment:
Needs Assessment

Description

For Puppet 5/Server 5: set use_legacy_auth_conf to false by default (current default for OSS in Puppet 4/Server 2.x is true).

Attachments

Issue Links

relates to

SERVER-1766 Don't use legacy auth.conf rules for puppet acceptance tests

Resolved

Activity

People

Assignee:: Adrien Thebo

Reporter:: Ruth Linehan

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2017/02/24 8:19 AM

Updated:: 2017/06/08 5:26 PM

Resolved:: 2017/04/03 4:50 PM

Zendesk Support