Update Set retrieval fails with SSO/LDAP Credentials Description<!-- 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; } --> When trying to retrieve update sets and testing the connection under 'update sources' from target to source, it fails with the error "authentication to the remote instance failed". Release or EnvironmentAllCauseSource instance is configured for SSO and SSO credentials can not be used for making web service calls between instances. ResolutionCustomers can enable LDAP authentication in combination with allowing inbound network access for ServiceNow instances to authenticate using LDAP credentials. In this case mid server can not be used for LDAP authentication. Please find the documentation below for setting up LDAP authentication. https://docs.servicenow.com/csh?topicname=c_LDAPIntegration.html&version=latest https://docs.servicenow.com/csh?topicname=r_LDAPIntegrationRequirements.html&version=latest Additional InformationOptionally, local credentials on an admin account can be used for the authentication.