Uploading a new X.509 SAML Certificate to your ScreenSteps Authentication Endpoint

Updated Jul 23, 2019

When you set up a SAML Authentication Endpoint in ScreenSteps you upload an X.509 Certificate in PEM format. This file is provided by your SAML provider. (If you are using Salesforce then the certificate is included in the Identify Provider Metadata file that you uploaded.) When that certificate expires you must upload a new certificate in order for your ScreenSteps SAML integration to continue to work properly.

Download the updated X.509 SAML certificate from your SAML provider

Which SAML provider is your ScreenSteps Authentication Endpoint connected to?

Download Metadata file from Salesforce

Download Metadata file

Download the certificate from Apps > SAML Apps > Settings for ScreenSteps

From this screen, click on the Manage certificates link.

In the dialog that appears, click on the Download Certificate button.

Download the certificate from ADFS Management > Service > Certificates

1. Open ADFS Management
2. Open Service > Certificates
3. View Certificate on token-signing primary
4. Click the Details tab
5. Click Copy to File...
6. Select Base-64 encoded X.509 (.CER)
7. Save to file (.CER)

Locate and download the x.509 certificate in PEM format

Unfortunately we don't have specific instructions on where to locate the certificate for your provider. You will most likely find the certificate in area of the SAML provider application where you configured the ScreenSteps integration.

Upload the certificate or metadata file to ScreenSteps

For information on locating your Single Sign-on settings refer to the article How to edit SAML settings or find your SAML Consumer and Test URLs.

Upload the file

If your endpoint is connected to Salesforce then click the Upload new Salesforce Configuration file button. Otherwise click the Replace SAML Certificate file button.

Select the certificate or metadata file and upload

After you select the file you downloaded from your provider it will upload and be applied to your endpoint. SSO should now work again.

Congratulations, you are done!

0 Comments

Add your comment

E-Mail me when someone replies to this comment

Still Need Help?

Contact Us