Difference between revisions of "JGridstart/Releases/1.0beta2"
(add issues) |
m |
||
Line 16: | Line 16: | ||
== Known issues == | == Known issues == | ||
− | * A refresh will remove the default certificate from the list in certain circumstances (but not from disk), including if it's the only one (fixed) | + | * A refresh will remove the default certificate from the list in certain circumstances (but not from disk), including if it's the only one (fixed in 1.0beta) |
− | * Renewal doesn't detect organisation properly | + | * Renewal doesn't detect organisation properly (fixed in 1.0beta3) |
− | * Import problems | + | * Import problems (fixed in 1.0beta3) |
Revision as of 12:24, 12 October 2009
JGridstart 1.0beta2 is a minor update of 1.0beta1 for testing with end-users. You too are welcome to test this version! Please notify us of any bugs you find, see Support
As a beta release, you need to know that this version may contain bugs. To be sure do make a backup of any existing private keys in your ~/.globus. As jGridstart is meant to be deployed by certificate authorities, this version communicates with a test certificate authority, so you can play with it as you like without bothering a real CA.
Getting started
To request a dummy certificate via jGridstart, please follow these steps:
- Launch jGridstart from the jGridstart 1.0beta launch page
- Request a new certificate (if this is not clear upon running jGridstart, it is considered a bug)
- When you have submitted your request, you don't need to visit a registration authority in person for this test. Instead, you can validate your own certificate by visiting the test certificate authority: locate your certificate, and press the lock icon to make your certificate valid.
- Close the wizard; restart jGridstart or refresh (F5/menu). This will show what to do next.
Importing your existing certificate is possible from a PKCS#12/PEM file containing your certificate or CSR _with_ your private key.
Please test and try to get it to misbehave :) It's beta-software so you'll probably succeed, this will help me to get it fixed before releasing the software in the wild. Known issues will be added below.
Known issues
- A refresh will remove the default certificate from the list in certain circumstances (but not from disk), including if it's the only one (fixed in 1.0beta)
- Renewal doesn't detect organisation properly (fixed in 1.0beta3)
- Import problems (fixed in 1.0beta3)