Signing issue!

[ajitkumar26]

Hi All,
I am getting the following error while creating the keystore file.

keytool error: java.lang.Exception: Input not an X.509 certificate

I have checked the *.csr file and the file does not contain any sppaces at the beginning and end but still getting the error.

Please help me ...


Thanks & Regards,
Ajit

[ajitkumar26]

Hi All ,
If I am giving the keystore file name without extension(e.g. keystore instead of keystore.ks) I am getting the following error

keytool error java.lang.exception certificate reply does not contain public key for <alias name>

Why this error is and how to resolve this? Please guide me...

I am using the following command to create the keystore file:
keytool -import -trustcacerts -keystore <keystore_filename> -alias <alias_name> -file <file name>


Please help me to resolve this issue.

Thanks in advance...

Thanks & Regards,
Ajit

[im2amit]

Hi All ,
If I am giving the keystore file name without extension(e.g. keystore instead of keystore.ks) I am getting the following error

keytool error java.lang.exception certificate reply does not contain public key for <alias name>

Why this error is and how to resolve this? Please guide me...

I am using the following command to create the keystore file:
keytool -import -trustcacerts -keystore <keystore_filename> -alias <alias_name> -file <file name>


Please help me to resolve this issue.

Thanks in advance...

Thanks & Regards,
Ajit

Try to use double quotes to encapsulate the filename.., then it should work.

[ajitkumar26]

Thanks Amit for your reply.

I have checked by using the double quotes to encapsulate the filename. But still the same error I am getting.
keytool error java.lang.exception certificate reply does not contain public key for <alias name>

Please help me to resolve this issue...

Thanks & Regards,
Ajit

[r2j7]

Hello ajitkumar26,

I am using the following command to create the keystore file:
keytool -import -trustcacerts -keystore <keystore_filename> -alias <alias_name> -file <file name>

Are you using the valid digital ID of a trusted certificate provider during the import? If yes, which?

You might also want to check these articles on Nokia Developer Wiki for more information about signing Java ME applications:

http://www.developer.nokia.com/Commu...ng_for_dummies

http://www.developer.nokia.com/Commu...ning_-_Java_ME

Regards,
r2j7

[ajitkumar26]

Hi Raj,

I have allready gone through the steps which is there in the mentioned links.
Actually we are doing renew.
I am surprising because the same step is working perfect for the last year digital ID but not working for this year new Digita ID.

And also when I am listing out the certificate contents then it is showing the data correctly.
So what could be the issue here. I am not able to get.

Please guide me...

Thanks & Regards,
Ajit

[r2j7]

Hello Ajit,

have you been in contact with the digital ID provider on this?

Regards,
r2j7

[ajitkumar26]

Hello Ajit,

have you been in contact with the digital ID provider on this?

Regards,
r2j7

Hi Raj,
When we contact the digital ID provider on this they sent a different digital ID but with the new one also the same problem exist.

What is the root cause of this? Do you have any idea?
What can be done to resolve this issue?

Please help me...



Thanks & Regards,
Ajit

[r2j7]

Hello Ajit,

as related to this original question of mine:

Are you using the valid digital ID of a trusted certificate provider during the import?

Who is the digital ID provider?
Is it Verisign or Thawte?

Based on the description, this seems to be related to the digital ID. Due to ths, I can only recommend to contact the digital ID provider about the problem as they can troubleshoot the issue in their product.

Regards,
r2j7