X.509 IDP certificate is not getting imported automaticallyDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> X.509 IDP certificate does not get imported automatically even though the scheduled job: Refresh MultiSSO IDP Metadata is Active and the correct Metadata URL is configured on the IDP record. We will also see the below warning in the application logs during the run of Refresh MultiSSO IDP Metadata job WARNING *** WARNING *** *** Script: idp_metadata_url is invalid. CauseExtra white space at the beginning or at the end of the URL configured on the Metadata URL from which IDP properties are imported field on the IDP record. ResolutionRemove extra white spaces.