Click HERE to see how Saviynt Intelligence is transforming the industry. |
05/23/2024 07:04 AM - last edited on 05/27/2024 04:02 AM by Sunil
Hi All,
We are trying to renew our SSO certificate
Steps we followed-
1. Clicked on edit , generated a new certificate marked it active and then downloaded metadata xml file
once done we are trying to upload the same file in Single sign on configuration
the issue is the certificate still shows the same expiration date while we have ensured the new certificate is getting generated .
Can anybody help find the root cause for this
Thanks
Sakshi
[This message has been edited by moderator to mask email address]
Solved! Go to Solution.
05/23/2024 08:26 AM
@Sakshi2806 : When you got the new IdP XML file downloaded do you see the certificate is reflecting to new one? I assume it is still reflecting to old certificate
05/27/2024 05:11 AM
When we generated a certificate. We tried to compare the keys as it was updated and different from current xml we tried to upload it in Saviynt but still it was showing the same expiration date.
I guess it was reflecting to old certificate but not sure what else could have been done. We already tried new session. The only thing that resolved it was completely deleting the old certificate and then generating a new,
05/23/2024 11:12 AM
It sounds like you've correctly generated and activated a new certificate for your Single Sign-On (SSO) configuration, but the system is still displaying the old expiration date. Here are a few potential causes and steps to troubleshoot this issue:
Cache Issue: Sometimes, browsers or the application itself might cache old data.
Metadata Upload: Ensure that the new metadata file is correctly uploaded to the SSO configuration.
Certificate Propagation: In some systems, it might take some time for the new certificate to propagate through all parts of the system.
Configuration Settings: Verify that the new certificate has been set as active in all required places within the SSO configuration settings.
Logs and Error Messages: Check the logs for any error messages that might provide more details about why the new certificate is not being recognized.
System Synchronization: Ensure that the systems involved in the SSO process are properly synchronized.
If none of these solutions resolve the issue, it might be helpful to share more details or screenshots of the configuration process and any error messages you are encountering.
05/27/2024 03:06 AM
Thanks Rushikesh,
In our case metadata xml file had issue. We had to completely delete the old instancce and then we tried to generate the new It eventually resolved the issue.
Thanks
Sakshi