SSF error:Invalid signer error while sending certificate via OAC0

[pranab_kumarjha]

Hi,

We are implementing document archiving in external documentum server. For this we are maintaining a content repository in OAC0.

The test connection between the sap and documentum was successful in OAC0 but when sending the certificate I am getting this error "SSF error:Invalid signer".

I have tried tick/untick the "No Signature" box but it also doesnot helps.

Can someone please tell the possible reasons or a solution.

Thanks,

Pranab

[nabheetscn]

Please check below mentione link..search u will find many

[;

Nabheet

[pranab_kumarjha]

Hi Nabneet,

I already checked that linked forum. Also the note mentioned doesnot include the same error. The error is coming in transaction code OAC0.

[Former Member]

Hello Pranab,

Please check this thread:

Regards,

Amit Barnawal

[Former Member]

This was the fix in the end.....

Note 1055856 - Common error messages when setting up Single Sign-On

No digital signature could be generated

              To issue a digital signature, the system requires a PSE. The PSE is stored on the file system of the application server and additional meta information about the file is saved in the database. If you now change the file directly at file system level, inconsistencies may occur.  In particular, when the system issues an SAP logon ticket that is digitally signed by the application server, the trace displays the following additional entry: 

              N *** ERROR => Ticket creation failed with rc = 1441801. [ssoxxkrn.c 704 

              To correct this problem, proceed as follows: 

               - Call transaction STRUST 

               - Double-click the entry "System PSE" 

               - From the menu, select "PSE > Save as.. ." 

               - Select the option "System PSE" 

               - Confirm the dialogs that follow 

              => As a result, the PSE is saved again in the file system and the database tables are cleaned up.