Forum Discussion
SmartBear_Suppo
Alumni
17 years agoHi Sachin,
thanks for the great post!
Regarding this issue, you could try the following instead:
1) Remove the keystore from the global ssl settings and add it to your projects WS-Security configuration under the keystores/certificate tab instead. Here you can use a relative path or properties as desired (relative paths will be resolved relative to the project ResourceRoot value)
2) Select this entry in your requests' "keystore" property (in the bottom left properties-table)
Now the keystore settings is stored in your project file instead, so you can skip the -t argument on the command-line.
Does that help?
regards!
/Ole
eviware.com
thanks for the great post!
Regarding this issue, you could try the following instead:
1) Remove the keystore from the global ssl settings and add it to your projects WS-Security configuration under the keystores/certificate tab instead. Here you can use a relative path or properties as desired (relative paths will be resolved relative to the project ResourceRoot value)
2) Select this entry in your requests' "keystore" property (in the bottom left properties-table)
Now the keystore settings is stored in your project file instead, so you can skip the -t argument on the command-line.
Does that help?
regards!
/Ole
eviware.com