Currently the properties for all TPS profiles are stored in CS.cfg which makes it harder to manage. It would be better to store them in separate files or in LDAP entries (which will allow replication). The REST service will need to be updated accordingly.
Proposed milestone: April
Per discussions, targeted 10.2 - 04/14 (April)
Moved to 10.3 per discussion:
edewata wrote: Is this assigned to me? This ticket was suggested by Christina and I believe she said that it would better if we can fix this soon (i.e. April milestone), but I think if it's not blocking anything we probably can defer this. cfu wrote: I agree that this would need to be moved. The task would touch many areas and probably would benefit from a design writeup for discussion before work. nkinder wrote: Ack. This is a nice to have, but it's a later feature (10.3 or 10.4). I suspect that this will become important as soon as IPA starts exposing the ability to use custom profiles, as they will surely want them to be replicated.
New proposed milestone: 10.3
This probably requires major works, similar to CA's LDAP-based profiles:
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
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/1522
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.