AnsweredAssumed Answered

GMU Migration - Ilegal Key size

Question asked by gilson.watanabe on Jun 14, 2018
Latest reply on Jun 18, 2018 by Mark.ODonohue

I found something similar in older post but no clue about solution.

 

I did somehow all configurations and I can migrate using GMU using my notebook. I can use migrateOut and migrateIn and it's working fine here.

 

But if I copy everything (GMU, libs, .p12 files, authentication properties - same folder with same configurations) it doesn't work. The error message is:

 

[root@li2745 GMU]# ./GatewayMigrationUtility.sh migrateOut -z properties/origem.properties --dest usuario.xml --serviceName /GET/usuario
Warning: TLS hostname verification has been disabled
Warning: TLS server certificate check has been disabled
Running........
Execution failed. Reason: Error creating keystore: exception unwrapping private key - java.security.InvalidKeyException: Illegal key size

 

Locally, it works fine:

 

D:\Aplicativos\GMU>GatewayMigrationUtility.bat migrateOut -z properties\origem.properties --defaultAction NewOrUpdate --dest usuario.xml --serviceName /GET/usuario
Warning: TLS hostname verification has been disabled
Warning: TLS server certificate check has been disabled
Running.................................................................................................
Done

 

The content of this properties file is:

 

host=li3384
port=8443
clientCert=origem.p12
password=u2r8pC8YvkY.DaP6pbFb6jBwfXFBk4aQ9Q
encryptionPassphrase=u2r8pC8YvkY.DaP6pbFb6jBwfXFBk4aQ9Q
trustCertificate
trustHostname

 

All passwords are the same and I'm not using or configure server trust (last topic of Configure GMU and Gateways for Migration - CA API Gateway - 9.3 - CA Technologies Documentation). Any ideas about what am I missing?

Outcomes