Is there any call you can make to the URLs to get it to tell you what authentication protocol it expects for its user id and password?
Otherwise it's try many different protocol modified URLs strings, tokens etc to attempt to see which is the correct method.
I have pinged a message to Enphase to see if they will reveal the correct method.
I will also try experimenting with the original type in the URL from a browser and try and add the user id and password in the call to see if I can find what structure of call works. Normally from a browser I enter the URL then it brings up a window asking for user id and password - enter the correct details and everything then works fine when you continually press refresh until you close the browser - so I guess it creates a session token or cookie somewhere that expires once the session closes? Wish there was a way is seeing exactly what happens and what it therefore expects!
Edited by g__day, 15 February 2017 - 10:37 PM.