# .xmm mapping passwords **URL:** \ **Category:** Forum\ **Tags:** Mainframe-Integration, EntireX\ **Created:** [August 11, 2010, 4:44pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341 "2010-08-11T16:44:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://techcommunity.softwareag.com/u/James3)\ **Post date:** [August 11, 2010, 4:44pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/1 "2010-08-11T16:44:42Z")
I have been trying to work with WS-STACK, v 8.0.5.0, deployed on a Websphere 7.0 Apps server. I can get my mainframe web services to work when I am using unsecured broker and RPC. However, if I create and deploy an archive (.aar) specifying user id and passwords for secure rpc and broker (using the “set connection and security parameters in mapping file” option) I get the following error when I try to call the web service. There are no errors showing in the JVM logs. I have attached my WS-STACK validation page. axis2ns4:ServerXML Runtime Exception 2000 0087 Internal error. Caused by:javax.crypto.IllegalBlockSizeException: Input length (with padding) not multiple of 16 bytes20000087Internal error.javax.crypto.IllegalBlockSizeException: Input length (with padding) not multiple of 16 bytes [Web Services Stack Validation Page.htm](https://techcommunity.softwareag.com/uploads/short-url/29IYQD8OLah71C8HjKHWM9R9CyP.htm) (44.2 KB) ---
**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\ **Post date:** [August 11, 2010, 9:26pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/2 "2010-08-11T21:26:13Z")
This might be a problem with the security installation of your JVM. I found a hint that replacing the JCE files might help. In general see [Java SDK](http://www.ibm.com/developerworks/java/jdk/security/60/secguides/securityguide.lnx.html) . And [Java SDK](http://www.ibm.com/developerworks/java/jdk/security/60/secguides/securityguide.lnx.html#jce) contains a link from where to get the “unrestricted jurisdiction policy files”. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://techcommunity.softwareag.com/u/James3)\ **Post date:** [August 19, 2010, 10:09pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/3 "2010-08-19T22:09:48Z")
Thank you, Rolf. I have tried as you suggested, implementing unrestricted jurisdiction security jars in the server runtimes and in RAD/Eclipse development environment, but the problem still occurs. I therefore tried downloading and installing the latest version of the Eclipse-based development tool, as packaged and distributed by Software AG, includuing their default WS-STACK implementation and Tomcat test server. Exactly the same problem still occurs. I feel that the problem is actually rooted in the development tool, which is failing to encrypt the passwords at the time the mapping is deployed. The web-service response is probably the result of trying to decrypt something that is either not encrypted or is missing. ---
**Author:** ![Markus2](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@Markus2](https://techcommunity.softwareag.com/u/Markus2)\ **Post date:** [October 18, 2010, 6:53pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/4 "2010-10-18T18:53:43Z")
In case it helps anyone, I had the same error calling a deployed aar with a secured broker and specifying the security parameters in the soap header (exx-userID and exx-password fields). The solution was to use encrypted passwords and not plain text passwords. Therefore I also believe the error lies in the Designer as James described it. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://techcommunity.softwareag.com/u/James3)\ **Post date:** [October 19, 2010, 3:50pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/5 "2010-10-19T15:50:20Z")
Just FYI, This problem was later resolved by a fix from Software AG in response to a support reuqest that I opened. ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [April 2, 2021, 2:58pm UTC](https://techcommunity.softwareag.com/t/xmm-mapping-passwords/94341/6 "2021-04-02T14:58:53Z")