<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00007tD4i6SACOkta Classic EngineSingle Sign-OnAnswered2020-04-02T02:04:42.000Z2020-02-25T10:40:26.000Z2020-04-02T02:04:42.000Z
Failed to create custom SAML 2.0 Application with SLO - Certificate filename is invalid

I'm trying to set-up my custom SAML 2.0 application and while I can upload a certificate downloaded from my Jamf Pro instance (this is an API response from uploading certificate):

{

 "notAfter": "2025-02-25T10:11:51.000Z",

 "uploadedOn": "Tue Feb 25 10:32:40 UTC 2020",

 "certName": "CN=Fleet Docker Jamf Pro JSS Built-in Certificate Authority (1).pem",

 "certificateId": "aic2l7eo6cwJOMIk94x6",

 "id": "aic2l7eo6cwJOMIk94x6",

 "certificatePrincipal": "SSO: iiinvbj.pub.jamf.build",

 "uploadedBy": "Amelinium Falcon",

 "issuer": "CN=Fleet Docker Jamf Pro JSS Built-in Certificate Authority",

 "notBefore": "2020-02-24T10:11:51.000Z"

}

When I try to save the configuration I reveive an error:

{

 "errorCode": "E0000001",

 "errorSummary": "Api validation failed: samlSPSignatureCertificateId",

 "errorLink": "E0000001",

 "errorId": "oaemvaE5lmqT7aLxHjvix_4ZA",

 "errorCauses": [

  {

   "errorSummary": "samlSPSignatureCertificateId: The filename is invalid or missing"

  }

 ]

}

with error meesage in UI

 

/help/servlet/rtaImage?refid=0EM1Y00000124Hd

 

Anyone has seen this kind of issue?


  • Hey there! Sorry for the lack of response here on the Discussions forum. If you’re still looking for an answer, I would recommend checking out our Developer resources, including the Developer Forum (https://devforum.okta.com/) and documentation. If you are unable to find the solutions you're looking for there, we would encourage you to contact our dedicated Developer Support team at developers@okta.com, and they will be able to help you out.

    Expand Post
This question is closed.
Loading
Failed to create custom SAML 2.0 Application with SLO - Certificate filename is invalid