Certificate with PSE type >SystemPSE< has been invalid

[Former Member]

Hi,

I got the following error in the log. Please advise.

Certificate with PSE type >SystemPSE< has been invalid for 733561 days

Regards,

Tony

[Former Member · Accepted solution]

Tony,

Did you verify the certificate from strustsso2?

It seems like something is not right with either the certificate or your system date. It seems unlikely that your system date is that far off.

Please click on the certificate listed in the Owner section of strustsso2 and verify the to date.

Hope this helps.

PJ

[Former Member · Accepted solution]

Hi Tony,

Even we have this error in our system since last 9-10 months. Unless and until your certificates are valid in STRUSTSSO2, no need to worry about it.

In our system we did not do anything for this error and still everything is fine.

[Former Member]

Maybe Sap Note 1127219 will help you?

[Former Member]

Do you only have the Portal certificate applied in STRUSTSSO2 ? Probably there is something else too which has expired. If your Portal can SSO fine to ABAP backend then this message definitely does not come from Portal certficate.

We also had this error in SM21. I cleaned up all the rubbish from STRUSTSSO2 and only left the required certificates and ensured they are valid.

[Former Member]

The date format is correct.

Regards,

Tony

[Former Member]

Tony,

If you are not currently using SSO, you may want to clean up the System PSE at any time, to eliminate those log errors.

If you are actively using SSO, youu2019ll want to wait for off-peak hours or a maintenance window.

The following is based on having the system certificate and the portal SSO certificate. If you have more for other reasons, youu2019ll need to take more care and planning.

To do this, you will need to:

- go to strustsso2

- right click on System PSE (left panel)

- select Delete

- green arrow back all the way out of strustsso2 to the main screen

- Go back into strustsso2

- right click on create

- accept the default entries for u2018create PSEu2019

- click Save

- If you expand the System PSE on left, you should see your server name.

- Double click the server to show the system certificate.

- Then double click the certificate to see the details.

- Finally, youu2019ll want to import your SSO certificate, add it to the Certificate List and add it to the ACL, and save.

Of course, all of this is if you want to have a cleaner system log. If you have any doubts before attempting, feel free to post as there are a lot of helpful people in the forums, and in this thread alone!

If everything is working as expected and you donu2019t mind ignoring the system log messages, then you can take no action.

Hope this helps!

: )

PJ

[Former Member]

We have configured the SSO only and we don't configure SSL.

Regards,

Tony

[Former Member]

I think thare shall be no issue because you Portal certificat is Fine.

Please once more check the date format is correct in portal Certificate.

ThankS

Rishi Abrol

[Former Member]

Sorry. It should be SM21

[Former Member]

Have you configure SSO between portal.Have you SSL configured.

Thanks Rishi Abrol

[Former Member]

I find this message in the system log using t-code SM20. We get this message everyday.

Regards,

Tony

[Former Member]

Hi Rishi Abrol,

I would like to know any impact on the system when this warning message occurs. Also, the certificate is valid to year 2028.

Regards,

Tony

[Former Member]

I dont think any impact on the system if SS0 is working .

Can you please explain Me where are you getting the error and How?

Thanks Rishi Abrol

[Former Member]

Hi,

Can you please check the certificate that it has valid Date if not then create a new certificate with proper details.

Please explain what are you trying to do.So that i can guide you more.

Thanks Rishi Abrol