This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 85986 - should not allow empty field for non default key store.
Summary: should not allow empty field for non default key store.
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Identity (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Peter Liu
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2006-09-27 23:23 UTC by _ hlu
Modified: 2006-09-28 19:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ hlu 2006-09-27 23:23:06 UTC
build20060925:
should not allow empty field for non default key store.
Comment 1 Srividhya Narayanan 2006-09-27 23:27:18 UTC
Basically, as part of enabling custom keystore we discovered that the AM runtime
expects a valid value for each of the fields in the certificate settings. For
example if the key alias password was the same as keystore password, it is
possible to leave the key alias password field empty. But the AM runtime expects
this field to be still filled in even when both password are the same. We have
to update the online doc on that but can we also check to make sure that all the
certificate settings field are filled in and none is empty upon submit much like
what we do for keystore? The other option is to update the Ui to say that all
fields are mandatory but I am not sure what the impact is with the UI freeze on
these.
Comment 2 Peter Liu 2006-09-28 16:55:37 UTC
We currently already have checks for all the fields except for the key password
field. We can simply do the same check on the key password field like all the
other fields.
Comment 3 Peter Liu 2006-09-28 19:07:52 UTC
Checked in changes to check for empty key password.