| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
| |
A new option has been added to the client-cert-import command to
import a certificate from CA by specifying the serial number.
The client-cert-import has also been modified to get the nickname
of the certificate to import from the CLI argument. For backward
compatibility, if no argument is specified the CLI will try to
get the nickname from the authentication option (-n).
Ticket #1152
|
|
|
|
|
|
|
|
| |
The user-cert-add CLI has been modified to provide an option to
specify the serial number of the certificate to be imported from
the CA.
Ticket #1151
|
|
|
|
|
|
|
| |
The ca-cert-request-review CLI has been modified to show the
request status after completing the operation.
Ticket #1149
|
|
|
|
|
|
|
| |
A new CLI has been added to simplify the process to request
a user certificate for client certificate authentication.
Ticket #1148
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This patch fixes manpage-has-errors-from-man and hyphen-used-as-minus-sign
found by lintian tool on Debian.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Ticket 1142
|
|
|
|
|
|
|
| |
This reverts commit 223d15539b7bcc0df025025036af2935726e52e3.
The patch does not work for subsystems installed on separate
instance since it will require additional OCSP setup.
|
|
|
|
| |
* PKI TRAC Ticket #1017 - Rename pki-tps-tomcat to pki-tps
|
|
|
|
|
|
|
|
|
|
|
| |
TpsClient will now suport the ability to specify extensions in the
script file.
Ex:
op=ra_format uid=jmagne pwd=netscape new_pin=netscape num_threads=1 extensions=tokenType=userKey
Ticket # 1016.
|
|
|
|
| |
recovery
|
|
|
|
|
|
|
|
| |
The CS.cfg templates for all subsystems have been modified to enable
certificate revocation checking during authentication. This will
affect new installations only.
Ticket #1117, #1134
|
|
|
|
| |
- PKI TRAC Ticket #1017 - Rename pki-tps-tomcat to pki-tps
|
|
|
|
| |
- PKI TRAC Ticket #1077 - Consider removing [Apache] section from 'default.cfg'
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code to remove the connector from the pki CLI was found to be broken
because of invalid message type (partly due to void returns).
On uninstall, we need to remove the kra-connector from all relevant CA's
in the security domain. The best way to do this is to keep kra-connector
info in LDAP, so that only one call is needed. Until that change has
been made, we are adding a hack to remove the connector from all CA's
in the secutrity domain (if it exists).
Due to issues with proxy configurations, we will continue to use sslget
and a url-encoded-form version of the servlet.
In addition, it was found that when removing a KRA from a shared subsystem,
the updateDomainXML servlet was erroneously returning failure when it
was unsuccessful in removing a non-existent user from a group.
Ticket 1113
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Basic token key recovery functionality is there.
2. Tested with mostly the "damaged" scenerio. The low level
code that writes the recovered certs to the token works and has been
tested with a real token. Some of the other more obscure cases need
some more testing, for instance, the temporary on hold scenario.
3. Renewal has been tested with a real token to work.
4. Much of the complex code to write cert objects and key objects,
as well as importing recovered keys, has been centralized to a method.
This leaves the calling code simpler and easier to trouble shoot.
5. Added a method to check token operation transition states.
6. Fixed an issue with formatting a blank token I introduced.
7. Fixed a few issues with updating certificate records for a token that were discovered.
8. Added tps code to retrieve a certificate for the recovery case.
9. Minor Review fixes.
|
|
|
|
| |
RetrieveCert code
|
|
|
|
|
|
| |
All the secrets/keys retrieved using the client API's using Java/python
clients will be of the type - byte array. This applies to output of the
retrieveKey method and the public key attribute of the KeyInfo object.
|
|
|
|
|
| |
Addresses upstream issues in the pki key-* CLI commands.
Updates the man page in all the required cases.
|
|
|
|
|
|
|
| |
The client-cert-import command has been modified to propertly
initialize the CLI environment to avoid a null pointer exception.
Ticket #1126
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously specifying a security database password in the CLI would
require a certificate nickname to be specified as well. While this
is correct for client certificate authentication, it caused a
problem for operations that do not authenticate against the server
such as client-init. The CLI has been modified to require a security
database password only if the nickname is specified for client
certificate authentication.
Similar changes have been made to require user password only if
the username is specified for basic authentication.
The CLI also has been modified to store all specified parameters
in the config object regardless of parameter validation.
The manual page has been modified accordingly.
Ticket #1125
|
|
|
|
|
| |
- PKI TRAC Ticket #1127 - Remove 'pki-ra', 'pki-setup', and 'pki-silent'
packages . . .
|
|
|
|
| |
- PKI TRAC Ticket #1120 - Remove Firefox PKI GUI Configuration Panel Interface
|
|
|
|
|
|
| |
The current upgrade framework requires that all supported versions
to upgrade from to have corresponding upgrade folders even though
they might be empty. New empty folders have been added for 10.1.1.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously modifying the description of an empty group failed
because the server tried to delete a uniqueMember attribute that
did not exist because the group was already empty. The servlets and
group subsystem has been fixed to retrieve the existing group data
first, perform the changes on it, then save it back to the database.
Also adding a new group will no longer require a description because
it's not required by the LDAP object class.
Ticket #818
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds methods to key client to generate asymmetric keys using
algorithms RSA and DSA for a valid key sizes of 512, 1024, 2048,4096.
The generated keys are archived in the database.
Using the CLI, the public key(base64 encoded) can be retrieved by using
the key-show command.
The private key(base64 encoded) can be retrieved using the key-retrieve
command.
Ticket #1023
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously emptying a field in TPS UI could not be saved because
the change was not saved and sent to the server. The UI framework
now has been fixed to save and send the empty field to the server
such that the database can be updated properly.
Additional parameters have been added to the tps-token-mod command
to modify all editable fields.
Ticket #1085
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Make sure the new TPS packages all the applet files, like the old TPS has done.
2. Create a small new package called "pki-tps-client", which will hold ONLY the
command line utility "tpsclient" and all of its supporting libraries.
3. Move the directory pki/base/tps to pki/base/tps-client
We will do this until we can rewrite "tpclien" on the new Java TPS system.
Add package pki-tps-client.
|
|
|
|
| |
* PKI TRAC Ticket #567 - ui needs to be scrubbed for missing images
|
| |
|
|
|
|
|
| |
As per review, modified to return CertEnrollmentResult objects.
Ticket 1109
|
|
|
|
|
|
|
|
| |
The missing token policy attribute has been added to token database. The
REST services, CLI, and UI have been fixed accordingly. Other missing
attributes in tokenRecord object class are unused.
Ticket #1085
|
|
|
|
| |
- PKI TRAC Ticket #555 - Other ways to specify CLI password
|
|
|
|
|
|
|
| |
The new command allows users to view the information about
kra connectors registered with the CA.
Ticket #479
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch implements server side keygen when so configured in the CS.cfg.
1. In this case, the encryption cert's private key is generated on the KRA and archived by the KRA.
2. The private key is then injected onto the token.
3. This will allows us to later implement certificate recovery.
4. Fixed some minor issues discovered with the code that interfaces with the TKS and DRM.
5. Final certificate tested to work with Relyea's "SmartCard" utility to perform legal crypto operations.
Minor change.
|
|
|
|
| |
Some formatting, uninitialized variables.
|
|
|
|
|
|
|
|
| |
Current pkidestroy fails to remove a system that has been configured to
use proxy ports because the wrong ports are passed into the
updateDomainXML servlet. This small patch fixes this problem.
Ticket #1095
|
| |
|
|
|
|
|
| |
* PKI TRAC Ticket #905 - 2 Step Configuration of CA instance using
pkispawn fails
|
|
|
|
|
|
|
|
|
|
| |
Updated man page for all the new CLI commands added
for the Key and KeyRequest resources.
Also added missing code to retrieve a secret wrapped in a
user specified passphrase.
Ticket #945
|
|
|
|
| |
- PKI TRAC Ticket #965 - Improve error message - remove ACL mapping to the user
|
|
|
|
|
|
|
|
|
| |
1. Created code to actually change the key over to a new key set.
2. Made calls to the code from the format and enrollment operations,
the Pin Reset processor will do so when completed.
3. Tested with real card. Was able to change to key set #2 and then back to stock
Ticket #878.
|
|
|
|
|
|
|
| |
switching between ESC and tpsclient needs to change CS.cfg param
value and restart TPS. This fix makes the issue go away.
The actual issue is the differences between "loginRequest" and
"extendedLoginRequeest".
|