...
...
...
...
David Banz I think the easiest way is to archive the structure for Sign and encrypt engine in IDM on public Doc, and then copy this new structure there for a fresh start. We will not keep the history for the older articles, but this history can be looked up in archive if needed, and also most articles are new anyway for IDM 5.0.0. I think this approach will make it easier to publish. Do you think this is OK?
...
| Info |
|---|
This article includes updates for Identity Manager 5.0.01. |
Keys and certificates for the sign and encrypt engine can be stored in a Hardware Security Model (HSM) for several use cases. This is a more secure solution for signing and encryption than PKCS#12 files, which are files in the file system, only protected by a PIN code.
...
bcmail-*.jar
bcpgp-*.jar
bcpkix-*.jar
bcprov-*.jar (including bcprov-ext-*.jar)
Additional information
| Expand | ||
|---|---|---|
| ||