#2586 LDAP-based configuration
Closed: migrated 2 years ago by dmoluguw. Opened 5 years ago by edewata.

Currently many of PKI server configurations are stored in files including CS.cfg, profiles, login banner. If a server is cloned, each configuration change needs to be propagated manually to all clones.

To simplify the management some of the configuration can be migrated to LDAP. This will allow topology-wide configuration. There's also LDAP-based profiles but it's not used by default. Migrating to LDAP-based configuration will also reduce the need to update CS.cfg (if there's anything left in it).

There should be a framework that defines the storage in the LDAP tree and the API to access the LDAP-based configuration. The code can be migrated incrementally to use the framework.

Related tickets:


+1 for FUTURE - critical

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

5 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/2706

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)

2 years ago

Login to comment on this ticket.

Metadata