401 Unauthorized to access PAPI - Isilon array discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2025 03:19 PM
Hi Everyone,
We are trying to discover Isilon devices but we are getting errors in the pattern, sample below
HTTP request failed for credential with username: <username> - status: 401 - body:
<html> <head> <title>401 Unauthorized to access PAPI.</title> </head>
I did see this KB article Invalid username/password error during EMC Isilon discovery - Support and Troubleshooting which mentioned the needed credentials and access for the account and we were able to validate that the active directory account we are using is included on the group with the privileges below
- ISI_PRIV_LOGIN_PAPI
- ISI_PRIV_AUTH
- ISI_PRIV_DEVICES
- ISI_PRIV_NETWORK
- ISI_PRIV_NFS
- ISI_PRIV_SMARTPOOLS
- ISI_PRIV_SMB
How will we able to check if the accounts have rest capabilities for isilon as mentioned below and what could still be the issue
- "https://" + $host + ":8080/platform/3/cluster/config”
- "https://" + $host + ":8080/platform/3/network/interfaces”
- "https://" + $host_ip + ":8080/platform/3/cluster/nodes/”
- “https://” + $host + ":8080/platform/3/zones”
- "https://" + $host + ":8080/platform/3/network/pools”
- "https://" + host_ip + ":8080/platform/3/cluster/nodes/”
- "https://" + $host + ":8080/platform/3/storagepool/nodepools”
- "https://" + $host + ":8080/platform/3/storagepool/storagepools”
- "https://" + $host + ":8080/platform/3/protocols/nfs/exports”
- "https://" + $host + ":8080/platform/3/protocols/smb/shares"

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2025 08:20 AM
Hi @edosky
It's fun that I face the exact same issue 1 day after you 😅
I'm in the process of verifying if the access is correctly granted, as per the KB article you provided. Thanks.
To check if the REST Access works correctly, you could either:
- try to launch the different URLs in your browser and use the credentials you have been provided (basic auth),
- see the logs of the discovery and identify where it fails, like here for me:
If it still fails after all this, I would create a case and involve the ServiceNow support team.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2025 06:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 06:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2025 06:37 AM