Enphase - Authentication challenge without WWW-Authenticate header

Add-ons Bindings
1

It appears my Enphase Envoy gateway was upgraded recently (I guess Enphase did it?) and I’m now on firmware D8.3.5232 (f18f5b) - though I’m not sure what I was on prior.

Since that change, I can’t now authenticate with the Envoy Thing can’t authenticate using the old <=7.x method. I’ve tried a few things to move to the 7.x+ method:

  1. In the username / password fields for the Thing, I completed the same details I use to login to Enphase services online (eg. my email and the password). I included the Sitename as it appears on the Site Details page in the Enlighten app/web. (this is an arbitary string with spaces - I’m pretty sure I’ve got it 100%). I left Auto JWT enabled.
  2. As the above didn’t work. I dislabled Auto JWT, left the Site Name populated and the user/pass should be ignored anyway, but entered the token string I generated by visiting Enphase Authentication | Home and logging in with the same details I entered in (1) above.

For both cases, when I save the Thing page, I get the error:

Could not retrieve data: HTTP protocol violation: Authentication challenge without WWW-Authenticate header

very quickly. The IP address is completed and I know this is correct as using Postman I get a valid response from https://<ip address>/infosuccessfullly.. well, as long as I also include the Bearer token for auth.

Am I doing the auth wrong somehow? Has something changed in Enphase? Not sure how else to try to get this working again.

2

I was able to fix this, so for anyone else who comes across a similar issue:

I recreated the Bridge Thing and it was able to successfully authenticate with Enphase with Auto JWT. I used exactly the same details as my original Thing - but as it was still reporting an earlier version of the Enphase firmware, I presume it was attempting to login using the legacy method.

In short - the Binding doesn’t seem to gracefully handle a firmware jump from <7.x to >=7.x. A rare event I guess.