|
|||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||
See:
Description
| Packages | |
| xecure.crypto | |
| xecure.file | |
| xecure.servlet | |
XecureWeb Java API Document
Multiple Character Set Instructions:
Any character set which is different to system default character set can cause wrong cryptographic operations.
This problem can take place in two categories listed below.
1. Encrypted Session (XecureHttpServletRequest, XecureHttpServletResponse)
2. XecureWeb Java API
Signer
SignVerifier
SignVerifierM
MultiSignVerifier
EnvelopeData
To avoid this case, strings should be properly translated by adequate character set.
XecureWeb can do this using page character set information.
As this feature is turned off by default, the following settings must be done to use it.
1. Encrypted Session
a. in xecure_servlet.conf file, set Geenral-usePageCharset value to 'true'.
<General
usePageCharset="true"
/>
b. in xecureweb.js file, set usePageCharset value to 'true'.
var usePageCharset=true;
2. XecureWeb Java API
Use the following overloaded constructors.
Signer.Signer(XecureConfig config, String charset)
SignVerifier.SignVerifier(XecureConfig config, String signed_msg, String charset)
SignVerifier.SignVerifier(XecureConfig config, String signed_msg, String cadn, String operaterId, String charset)
SignVerifierM.SignVerifierM(XecureConfig config, String signed_msg, String charset)
MultiSignVerifier.MultiSignVerifier(XecureConfig config, String signed_msg, String charset)
EnvelopeData.EnvelopeData(XecureConfig config, String charset)
'charset' can be substituted by response.getCharacterEncoding() method to use page charset.
|
|||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||