*What is the impact on the customer of the bug?
This fix is required if multiple keystore\truststore passwords need to be configured using Embedded API.
*How likely is it that a customer will see the bug and how serious is the bug?
Only when the API is used. No security or performance impact. OpsCenter, internal customer, will need to use the API with its next integration.
*What is the cost/risk of fixing the bug?
Cost is low. No impact on non-embedded or embedded that doesn't require this API.
*How risky is the fix? How much work is the fix? Is the fix complicated?
Very low. Additional get/setters for the attributes.
*Is there an impact on documentation or message strings?
*Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
None. Embedded tests running in Hudson should be fine. A test has been added.
*Which is the targeted build of 3.1.2 for this fix?