I've tried on a distributed setup as well as just a single host test instance that has TCP connectivity to the target storage frame's API (for example https://192.168.1.100:8080 ). I'm running a tcpdump after I input the storage address with validated credentials but never see any TCP communication after restarting splunk. Greping ps as well, I do not see any running python scripts from the app initiated or attempting to connect to the Isilon.
Between attempts I would remove the local/app & local/passwords conf that are created upon "setup" and restart splunk. I never saw any TCP communication or python process associated with the path of the app launching after "setup" of the addon.
Wow so the fix was so easy its kind of embarrassing, but I'll take it! Essentially had to just turn on the scripts to start inputting. Was able to get this working on Splunk 6.3.2 (App currently validated for 6.2) although I haven't checked full App functionality yet, looks promising.
Go to "Settings"
Under "Local Inputs" go to "Scripts"
Under the status column "Enable" the scripts of interest