| Summary: | [plan] Support for p12 certificates | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mathias Stümpert <mathias.stuempert> |
| Component: | Geclipse | Assignee: | Mathias Stümpert <mathias.stuempert> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tkoecker |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Mathias Stümpert
*** Bug 197896 has been marked as a duplicate of this bug. *** Both Globus proxies and VOMS proxies may now by generated from p12-certificates. All you have to do is to specify a p12 file instead of a pem file within the proxy wizard. For p12 files no key file is needed since the key is encrypted in the p12 file itself. There is a serious issue with p12 certificates. As described in the "IMPORTANT NOTES" at http://bouncycastle.org/documentation.html one needs to download the unrestricted policy files for the Sun JCE. Otherwise one gets something like java.lang.SecurityException: Unsupported keysize or algorithm parameters at javax.crypto.Cipher.init(DashoA6275) when trying to create a proxy from a p12 file. At the moment there is no easy workaround for this issue. closing this item |