OneFS API Update Shares, Path Not Found and Duplicate Users

Hi,

We're trying to use the Isilon API to update some permissions values on some shares for them, but we're running into two odd errors:

1. Path not found - The API returns an error AEC_NOT_FOUND and  with message Path '/ifs/data/xxxx/xxxx_xxxx/x$/xxxx/xxxxxxx' not found.  I obfuscated some of the chars with x's, but they are all normal ascii. We check spot checked 10 out of the many errors and the paths are all there.  Every single one of them DOES have the $ but in the path AND the share name.  But I'm able to perform that same operation against my virtual appliance just fine.

2. The GET request from the Isilon has various users listed more than once and a trustee that says group when I think it should be wellknown.  If we then attempt to issue a PUT with a similar array, we get an error. Here's an example body:

    "permissions": [

      {

        "permission": "change",

        "permission_type": "allow",

        "trustee": {

          "name": "DOMAIN\\usera",

          "type": "user"

        }

      },

      {

        "permission": "read",

        "permission_type": "allow",

        "trustee": {

          "name": "DOMAIN\\usera",

          "type": "user"

        }

      },

      {

        "permission": "full",

        "permission_type": "allow",

        "trustee": {

          "name": "DOMAIN\\domain admins",

          "type": "group"

        }

      },

      {

        "permission": "full",

        "permission_type": "allow",

        "trustee": {

          "name": "Administrators",

          "type": "group"

        }

      }

]

Its seems odd for it to look like this with the multiple users. The OneFS GUI shows the multiple entries as well. I think if I scrub the multiple entries by eliminating the 'least permissive entries', that should work, but its not obvious to me how this happened in the first place. I honestly have no idea how they created these shares in the first place.  And I think the domain admins is supposed to be a well known value, otherwise we get some error there.