EMC Isilon discovery REST GET method returns nothingDescription<!-- 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; } --> Symptoms Some of the steps for Isilon discovery use REST (GET method) to get device information. These steps leverage Basic Authentication credentials that are created by the customer for authentication for REST methods. In some cases even with basic auth. credentials defined the REST method returns no information, where testing on 3rd party REST client does (For example on Postman). The discovery log will look something like the below, the Red Box is the IP address of the host server. Release All where this pattern is installed Cause In some cases the Isilon device requires a certificate to be uploaded to the MID servers which execute the REST method. If there is none then we return nothing from discovery REST step for this device. Resolution Create a certificate and upload to the MID server. Please see the Isilon documentation below on how to get a certificate for the device: EMC Isilon Certificates See the docs below on how to import certificate to ServiceNow MID server: Add SSL certificate to MID Server