STRUST asking for password for Public Key

[Former Member]

I am working on an FTPs scenario using PI7.0 SP10.

I have set the everything up okay, loaded the x.509 certifcate, but when I try importing the Public Key into either STRUST of the J2EE Keystore, I get a pop up box asking for a password.

I have spoken to the third party administrators who insist there is not password on this file. I can open and view the key in notepad. I have tried entering any password, and entering past it, but these options fail.

I have searched OSS but no luck.

Any thoughts on what causes this?

[Former Member]

Have you tried giving Visual Admin Password?

[Former Member]

> Have you tried giving Visual Admin Password?

Not sure of the relevance, but have tried it and it fails.

Thanks anyway!

[Former Member]

Did you get any solution on this?? Because I am also facing the same problem..

[Former Member]

No luck yet!

[Former Member]

Are you able to load your Root Certificate correctly in VA? I am trying to upload it in Trusted CA's. And there it is asking for password.

One more thing,Can you please confirm the no of bits used in certificate for encryption? Because as per SAP Note 587377, cryptographic lib supports only 2048 bit encryption.

I found this useful and thought to tell you as you are also facing same problem.

Mean while if you are able to solve this issue, please update.

-Gouri

[Former Member]

There is a program: SSF_ALERT_CERTEXPIRE that has highlighted an issue, which I am not sure if this is relevant or not, but gives me something to work on!

[Former Member]

Gouri - what is the OSS note?

the note you have quoted - Note 587377 - FSCM-BD: XML download is not relevant.

Found it - 578377!

Message was edited by:

Barry Neaves

Added correct OSS Note number

[Former Member]

dont know if it helps but default password for the keystore in java is ‘changeit’, might be worth a go

[Former Member]

Can you please open your certificate with any text editor (In notepad) and paste the content on SDN?

-Gouri

[Former Member]

> Can you please open your certificate with any text

> editor (In notepad) and paste the content on SDN?

> -Gouri

Not overly keen on this idea, to be honest!

I have removed one row of characters for security reasons.

-

---

BEGIN PUBLIC KEY-----

MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC3q+etWyauKoo8i4DDokJCBugxv4XTXvSY

2n/u07LiFTEJBcLs3aIVmPTocIuxna/KiBlMJYMIWoCxkXrcxV/wBez2ser0WtihYZ0wvvMZ

-

---

END PUBLIC KEY-----

Just because I am not paranoid, doesn't mean everyone is not out to get me!

[Former Member]

Hay Barry,

Just wanted to tell you that when you upload your certificate you should follow the sequence. First you should upload issuing certificate then policy and then root.

In root certificate make sure that your certificate starts with "----Begin".

If there is anything else before that then delete it. and then try.

For example:

Please open this certificate with any text editor and remove the first

three lines from the certificate. They are:

"No Trusted Uses."

"No Rejected Uses."

"Alias: Medium"

After that you will have file beginning with the line

"---BEGIN TRUSTED CERTIFICATE---"

which can be imported successfully.

I think this should solve your problem. If not please get back.

-Gouri

[Former Member]

Gouri

All files start with either:

-

---

BEGIN CERTIFICATE-----

or

-

---

BEGIN PUBLIC KEY-----