#2418 [TPS] Some template substitution didn't happen during installation
Closed: Fixed None Opened 7 years ago by cfu.

Found the following entries in TPS CS.cfg not substituted after installation:

op.enroll.externalRegAddToToken.keyGen.encryption.serverKeygen.enable=[SERVER_KEYGEN]
op.enroll.delegateIEtoken.keyGen.encryption.serverKeygen.enable=[SERVER_KEYGEN]
op.enroll.delegateISEtoken.keyGen.encryption.serverKeygen.enable=[SERVER_KEYGEN]

Workaround is to manually change those values.

The preferred fix to this issue is to add the [SERVER_KEYGEN] substitution value as a slot variable to the pki/base/server/python/pki/server/deployment/pkiparser.py file plus any additional processing code such that it will be appropriately substituted.


[alee@localhost pki]$ git push origin master
Counting objects: 50, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (46/46), done.
Writing objects: 100% (50/50), 8.80 KiB | 0 bytes/s, done.
Total 50 (delta 39), reused 0 (delta 0)
To ssh://vakwetu@git.fedorahosted.org/git/pki.git
cb72f5b..7cfff9f master -> master

The following commit breaks deployment: d85080be85eb54756d9db69302a6117cef063017

pkispawn    : ERROR    ....... KeyError:  Master dictionary is missing the key called ''pki_enable_server_side_keygen''!

Need to put the substitution code in a conditional.
Pushed under one-liner rule.

[master ad454de] Fix deployment issue
Date: Tue Aug 2 11:18:31 2016 -0400
1 file changed, 5 insertions(+), 2 deletions(-)
[alee@localhost pki]$ git push origin master
Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (9/9), 749 bytes | 0 bytes/s, done.
Total 9 (delta 6), reused 0 (delta 0)
To ssh://vakwetu@git.fedorahosted.org/git/pki.git
cbf3763..ad454de master -> master

  • d85080be85eb54756d9db69302a6117cef063017

Metadata Update from @cfu:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.3.5

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/2538

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.

Login to comment on this ticket.

Metadata