Unable to authenticate to target instance during Clone Request or creation of Clone Target using the "Basic Authentication" methodIssue While many ServiceNow Administrators may now be using the new OAuth authentication method, there are still Administrators who will still be using the Basic Authentication method for authenticating the Clone Request for various reasons. However, some of these Administrators may run into an issue in which, despite the account name and password being correct, the credentials will still not properly Authenticate to the target instance. Symptoms In attempting to schedule a new Clone Request or create a Clone target instance, in attempting to authenticate to the target instance, the system reports that the name and password are incorrect, although the Administrator has verified that these credentials are indeed correct. Release All current and recent releases of the ServiceNow Platform. Cause Due to certain security enhancements that have been implemented in the ServiceNow systems, there are additional requirements for the accounts that can login to a remote instance. This would include attempting to connect using a third party tool as well as connecting from one instance to another for things such as creating a Clone Request or to configure an instance for retrieving Update Sets from another instance associated to the same account. Thus, administrators may find that accounts and roles that had previously allowed this remote connection are no longer working as they had previously. Thus, the administrators may need to adjust the roles that are associated to the account on the remote instance to ensure it allows connection from a remote source (such as another ServiceNow instance). Resolution To correct this issue, the Administrator will thus need to ensure that the account being used, on the remote instance has all the roles required to allow the account to successfully authenticate and perform the necessary tasks on the remote instance. For an account being used for authenticating for creation of a new Clone Target instance or an account used for authenticating a new Clone Request, the following roles should be associated to that account: snc_internal (only if the "Explicit Roles" plugin is installed on the instance) admin clone_admin snc_basic_auth_api_access Also, ensure the account is Active and not locked out, and ensure the "User must change password on next login" option is not selected on the account. It is recommended, but not mandatory, to also set the "Identity type of this User account record to "Machine". Once the account has the correct roles, the Administrator should then be able to successfully submit a Clone Request using this remote account.