JGridstart/Releases/1.0beta4

From PDP/Grid Wiki
Revision as of 09:32, 21 October 2009 by Wvengen@nikhef.nl (talk | contribs) (add known issues)
Jump to navigationJump to search

JGridstart 1.0beta4 is an update of 1.0beta3 for testing with end-users, fixing several bugs. 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:

  1. Launch jGridstart from the jGridstart 1.0beta launch page
  2. Request a new certificate (if this is not clear upon running jGridstart, it is considered a bug)
  3. 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.
  4. 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

  • Default browser may be wrongly detected on Windows (fixed in 1.0beta5)
  • File copy problem Windows XP when user cannot read security attributes (fixed in 1.0beta5)
  • It isn't always possible to check the CPS agreement checkbox during renewal (fixed in 1.0beta5)
  • Renewal S/MIME signing doesn't work (!) (fixed in 1.0beta5)
  • Some error messages are not clearly shown to the user (fixed in 1.0beta5)