#1218 Hard-coded 'enableBy' attribute in profile templates
Closed: migrated 3 years ago by dmoluguw. Opened 9 years ago by edewata.

Currently the profile templates in base/ca/shared/profiles/ca/ have the following attributes:

enable=true
enableBy=admin

When an instance is created, the templates will be imported into the instance (by copying into <instance>/ca/profiles/ca/ or adding into LDAP). If the instance was created using a non-standard admin name (e.g. caadmin) the profiles will contain an invalid 'enableBy' value. An invalid 'enableBy' may not cause any error, but the audit log may become incorrect.

One option is to remove the 'enableBy' attributes from the templates, then during import if the profile has enable=true it will be enabled by invoking the normal profile enable operation. This way the enableBy will be set properly.

Another option is to replace the value in the the templates with a slot variable (e.g. enableBy=${pki_admin_uid}) and substitute it with the actual value during instance creation.

Proposed milestone: 10.2.x


Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2.2

Per 10.2.2 Triage meeting of 02/24/2015: 10.3

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1780

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata