Replies: 1 comment
-
It works for me. Is it something with your client? ./ejbcaClientToolBox.sh EjbcaWsRaCli edituser p12user Aing12test false "CN=p12user" NULL NULL ManagementCA 1 P12 NEW EMPTY ENDUSER NULL ./ejbcaClientToolBox.sh EjbcaWsRaCli pkcs12req p12user Aing12test 2048 RSA NONE . openssl pkcs12 -in ./p12user.p12 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings. I have a problem with the generation of the pkcs12 token key using the wsdl webservices.
The generation works well. But it doesn't work when I pass more robust keys example: "Aing12test"
getting the following error:
body: '<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Bodysoap:Faultsoap:ServerGot request for user with invalid password: V28152139.<ns1:EjbcaException xmlns:ns1="http://ws.protocol.core.ejbca.org/">LOGIN_ERROR</ns1:EjbcaException></soap:Fault></soap:Body></soap:Envelope>'
}
The password policy in the Entity is free.
In short a key of type: 123456 or A123456 works. But it doesn't work with a more robust key.
work fine:
xmlns:tns="http://ws.protocol.core.ejbca.org/">soap:Bodytns:editUserAC-MYEnt-SignDirectSigner[email protected]nameSanV6221522falseV6221522falsefalseP12CN=V6221522,O=Link,C=VE,EMAILADDRESS=[email protected]10</tns:editUser></soap:Body></soap:Envelope>',
Beta Was this translation helpful? Give feedback.
All reactions