Patch for https://fedorahosted.org/pki/ticket/1102
b64encode() and base64.encodestring() work slightly different.
encodestring() includes an extra newline at the end of the string. It
seems the server treats both representations equally.
I ran the KRA tests according to base/kra/functional/drmtest.readme.txt.
The tests are passing, too.
I had some outstanding patches for Python 3 in my queue. Today I split
them up in digestible portions. The attached patches all hand-written.
I'm planning to submit the auto-generated patches by python-modernize at
a later point.
Add code to reindex data during cloning without replication
When setting up a clone, indexes are added before the
replication agreements are set up and the consumer is initialized.
Thus, as data is replicated and added to the clone db, the
data is indexed.
When cloning is done with the replication agreements already set
up and the data replicated, the existing data is not indexed and
cannot be accessed in searches. The data needs to be reindexed.
Related to ticket 1414
Please review the attached patch which addresses the following issue:
* PKI TRAC Ticket #1522 - CA UI adds extra space in Base 64 encoded
certificate display <https://fedorahosted.org/pki/ticket/1522>
I have tested a number of the displays, and have found no issues.
Acked by alee,
pushed to master.
Closing ticket #1523
----- Original Message -----
From: "John Magne" <jmagne(a)redhat.com>
To: "pki-users" <pki-users(a)redhat.com>
Sent: Friday, July 31, 2015 2:01:17 PM
Subject: [Pki-users] [pki-devel][PATCH] 0046-Firefox-warning.patch
Move the dire warning about the crypto object to sections where it applies.
Also slightly changed the message due to context.
Pki-users mailing list
op.format.externalRegAddToToken.revokeCert parameter missing in TPS CS.cfg.
It is true that his setting is not present.
The generic code that revokes certs for a format checks this value.
No harm in putting this value in the CS.cfg and setting it to false by
default for the externalRegAddToToken profile. No harm in giving the user
the way to use this feature , even if we decide it is not a good idea to revoke
certs associated with the external reg feature.
This patch fixes a regression introduced in
https://fedorahosted.org/pki/ticket/1307 [RFE] Support multiple keySets
for different cards for ExternalReg
where it missed assigning the calculated result to be returned.
It has been tested to work.
There is also one simple typo fix in there that doesn't have anything to
do with the feature in question.
TPS UI: After successful key upgrade during pin reset operation the token db still shows old key
Simple matter of not updating the token record at the end of the pin reset operation.
Also, make sure the activity log is correct.