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.
Steps to reproduce: 1. Creating custom keystore "mykeystore.jks" and import certificate from "amclientkeystore.jks". keytool -genkey -keystore mykeystore.jks -alias myalias -storepass password -keypass password keytool -export -rfc -keystore amclientkeystore.jks -alias amclient -file amclient.cer keytool -import -keystore mykeystore.jks -alias amclient -file amclient.cer. 2. Configure AM. - Edit SAML-HolderOfKey profile to use custom keystore: location - ../mykeystore.jks password - password alias - myalias alias password - password 3. Configure WSC. - Create StockServer and StockClient samples. - Edit WS attributes in StockServer to use SAML-HolderOfKey profile. - Edit WSC attributes in StockClient to use SAML-HolderOfKey profile and custom keystore. location - ../mykeystore.jks password - password alias - myalias alias password - password 4. Running. - Deploy both applications and run StockClient. In opened browser push "Submit". 5. Result: Exception occurs: "Securing request failed" After this any secured web service (even newly created and configured with default keystore) can't be invoked because of this error ...
It looks like there is a bug in the amclientsdk for setting the custom keystore information. I tried pointing the custom keystore to the default amclientkeystore.jks and it doesn't work either. I'll file a bug against AM and file a waiver request for this bug.
File a bug against access manager in bugtraq: http://bt2ws.central.sun.com/CrPrint?id=6525783
I am downgrading this to p2 since users can still use the default keystore.
Added to staged NB Enterprise Pack 5.5.1 Beta Release Notes (http://nbstaging.czech.sun.com/community/releases/55/1/entpack_relnotes.html#95733) Description needs verification. Workaround (if any)needed.
No Objections in 48 hours. Waived.
Removed Beta EP551_WAIVER_APPROVED keyword - we are going forward to FCS.
Added to NB IDE 6.0 Preview RNs as follows: Issue #95733: Secure Web Services do not work when using custom key store. Description:The custom key store support for web service security does not work. Workaround: Use the default key store by selecting the Use Default Key Store checkbox in the UI panels.
Removing status whiteboard: EP551_BETA_RN and change version to 6.0.
This issue is fixed in the latest AM bits in SDK b18. Note that AM, by default, uses RSA keys whereas keytool generate DSA keys be default. In order for customer keystore to work correctly, you need to create a RSA key by using the following command: keytool -genkey -keystore mykeystore.jks -alias myalias -keyalg rsa -storepass password -keypass password
VERIFIED