After Upgrade to Xanadu, Customer gets 403 on their instance integrationIssue Customer is testing Xanadu in their sub prod instance and discovered one of our vendors, is no longer able to update sc_task records in our sub prod instancebrowser shows: 403 Forbidden snow_adc Method failed: with code: 403 - Forbidden username/password combo <html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center><hr><center>snow_adc</center></body></html>ReleaseanyCauseThe root cause of the issue is that the vendor's instance, was trying to connect to the customer's instance, using an HTTP connection instead of an HTTPS connection.Resolution1. Identify the vendor's instance that is trying to connect to the customer's instance using an HTTP connection.2. Update the URL from HTTP to HTTPS in the vendor's scripted API.3. Test the connection to ensure that the vendor can now update sc_task records in the customer's sub-production instance via the scripted API.Note: The customer should ensure that all instances are using the secure HTTPS protocol for data transmission to prevent security vulnerabilities.