Hello @kzsh7 (kzsh7)​,

Thanks for posting.

This is the flow that must be followed when configuring SAML 2.0:

https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-General-Information.html

Usually, this link is opened from the integration process you are following with an app. Since you have some doubts about why is it necessary to use the X.509 certificates here is some information:

The X.509 certificates are the IdP certificates that a SAML configuration uses. After you install a certificate, you can add as many certificates as necessary. When there are multiple certificates, the system uses the first active certificate that is found. If you set the URL for the Metadata URL from which IDP properties are imported field, the system automatically polls the IdP for a current, valid certificate when your certificate is no longer valid. It appends this certificate to your instance and uses it for your active SAML configuration.

https://docs.servicenow.com/bundle/rome-platform-administration/page/integrate/single-sign-on/concept/x-509-certificate-sso.html

"You will also need to provide the vendor/developer with the following information from the Okta application (accessed via the View Setup Instructions button in the application's Sign-On tab):

The Identity Provider Single Sign-On URL. The SP may refer to this as the "SSO URL" or "

SAML Endpoint." It's the only actual URL Okta provides when configuring a SAML application, so it's safe to say that any field on the Service Provider side that is expecting a URL will need this entered into it.

The Identity Provider Issuer. This is often referred to as the Entity ID or simply "Issuer." The assertion will contain this information, and the SP will use it as verification.

The x.509 Certificate. Some service providers allow you to upload this as a file, whereas others require you to paste it as text into a field.

"https://support.okta.com/help/s/article/Beginner-s-Guide-to-SAML?language=en_US

Please let us know if this helps.

Regards,

Natalia

Okta Inc.