8000 Warnings for subsystem-specific parameters defined in [DEFAULT] section. · Issue #2933 · dogtagpki/pki · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Warnings for subsystem-specific parameters defined in [DEFAULT] section. #2933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
pki-bot opened this issue Oct 3, 2020 · 4 comments
Closed

Warnings for subsystem-specific parameters defined in [DEFAULT] section. #2933

pki-bot opened this issue Oct 3, 2020 · 4 comments
Labels
Stale
Milestone
10.6

Comments

@pki-bot
Copy link
pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2813. Originally filed by edewata (@edewata) on 2017-09-21 17:14:37:

  • Assigned to nobody

Currently the pkispawn man page provides examples with some parameters defined in [DEFAULT] section, e.g:

[DEFAULT]
pki_admin_password=Secret123
pki_client_pkcs12_password=Secret123
pki_ds_password=Secret123

These parameters should have been defined in [] section since they are subsystem-specific, i.e.:

[CA]
pki_admin_password=Secret123
pki_client_pkcs12_password=Secret123
pki_ds_password=Secret123

The man page should be updated and pkispawn should generate warnings if these parameters are defined in [DEFAULT] section in the user configuration file.

Note that the location of the parameters in the default.cfg is irrelevant. They could be moved into [] as well, or they can stay in [DEFAULT] for other reasons (e.g. backward compatibility).
@pki-bot
Copy link
Author
pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-09-25 18:38:57

Metadata Update from @mharmsen:

  • Custom field component adjusted to None
  • Custom field feature adjusted to None
  • Custom field origin adjusted to None
  • Custom field proposedmilestone adjusted to None
  • Custom field proposedpriority adjusted to None
  • Custom field reviewer adjusted to None
  • Custom field type adjusted to None
  • Custom field version adjusted to None
  • Issue set to the milestone: 0.0 NEEDS_TRIAGE

@pki-bot pki-bot added this to the 10.6 milestone Oct 3, 2020
@pki-bot
Copy link
Author
pki-bot commented Oct 3, 2020

Comment from vakwetu (@vakwetu) at 2017-09-28 17:00:39

Metadata Update from @vakwetu:

  • Issue priority set to: major
  • Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)

@github-actions GitHub Actions
Copy link
github-actions bot commented Mar 9, 2025

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Mar 9, 2025
@github-actions GitHub Actions
Copy link
github-actions bot commented Apr 9, 2025

This issue will be closed for inactivity. If the problem is still present reopen this or create a new issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale
Projects
None yet
Milestone
10.6
Development

No branches or pull requests
1 participant
@pki-bot
0