SSF error: Invalid signer, Message no. 1S005

[Former Member]

Hello Everyone,

We are in the process of configuring the content server in our customer's landscape.

Post the definition of content repository and the associated storage category,in the CSADMIN section,in the certificates tab, an error that reads SSF error: Invalid signer, Message no. 1S005 is thrown up whenever we attempt to send the certificate.Toggling values of 'Security' and ' Check Signature' fields doesn't help either.

Could anyone shed light on this issue and possible solution?

Note:We have not enabled/configured digital signature strategy and all the previous posts in the forum on this topic are in-conclusive.

Regards,

Pradeepkumar Haragoldavar

[Former Member · Accepted solution]

Dear Pradeepkumar Haragoldavar

Greetings !!!

Access T code OAC0 --> Select your content repository and mark or un mark the check box "No Signature". This should solve your issue.

please note that at times the behaviour of this check box is different in different servers.

For ex: In one box you will not get the mentioned error message if you mark the check box and in another box it might be otherway around.

I am not sure why system behaves indifferently on this check box

Hope this work arround help You

Best Regards

Tushar Dave

[Former Member · Accepted solution]

Dear Pradeep

The error message "Invalid signer" actually exactly means what the

message text says: the system where the error occurred was unable

to verify the signer of a signed document, most likely because the

related certificate could not be found.

Please check the following:

- Does a PSE exist on the signing system for the intended purpose?

(check: communication with a content server) (TA STRUST)

- Does PSE use a subject name that consists of 7bit ASCII

characters only?

- Has the certificate been distributed to the receiving system ?

Which security toolkit do you use (SAPSECULIB or SAPCRYPTOLIB)?

Please check the version of your installed security toolkit (TA STRUST,

menu "Environment > Display SSF Version").

Please also check for any error messages that may occurr at the

SSF initialization phase (ST11)

if you are using SAPCRYPTOLIB for SSF, please see note 662340

Regards

Tushar Dave

[Former Member · Accepted solution]

Thanks for your inputs Tushar!! We have already tried out these options,no success so far.

Suspect its a client specific issue.Will test on a new one and update.

Regards,

Pradeepkumar Haragoldavar

[Former Member · Accepted solution]

Dear Pradeepkumar

Have you solved this issue? We are meeting this problem in the same situation.

[Former Member · Accepted solution]

It was a 'Development client' specific error.However,we replicated the entire scenario and tested in 'Quality client',there were absolutely no issues!!

Regards,

Pradeepkumar Haragoldavar

[Former Member]

Suggest you talk to Basis team, if Profile is set up correctly on server...

I believe a system profile is set up on server by basis team...

for certificate an entry has to be present in the the below table...

check table - SSF_PSE_H