-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to Whitelist username creation #1
Comments
The project still works, but there just hasnt been any movement recently On Mon, Nov 2, 2015 at 11:06 AM, Steve [email protected] wrote:
|
Great! Thanks for your fast reply. Just after I posted the above I also noticed you have 2 Hue apps in the Google Play Store. I haven't got round to testing these yet (will do so tomorrow), but also please make sure they use the randomly generated bridge usernames the next time you update them (if not already). If you could let me know when this is done it would be appreciated, and apologies for the inconvenience. Obviously this is a bit of a pain for developers of existing Hue apps, but the change is needed for improving the security of the Hue system. I will post the exact date (when the change will be made public) in the news section of www.developers.meethue.com as soon as it is known. |
Hi there,
I work for Philips Hue Developer Support. In case you are not aware we are changing the way we authenticate against the bridge in a few months time. Basically, custom whitelist entries will no longer be allowed. See below links for more info.
http://www.developers.meethue.com/documentation/important-whitelist-changes
http://www.developers.meethue.com/documentation/getting-started
I had a quick look at your code and it looks like you are passing in both the devicetype and username (in the RegistrationRequest object in BridgeRegistrar.java, lines 105, 108). For future bridge versions, the username should be removed and the randomly generated bridge usernames will be returned in the Bridge response (again, see above links).
I see you have not committed for over a year so not sure if this project is still active. If it is you may want to change this at some point so it remains compliant with future bridge versions.
Let me know if any doubts.
Thanks
Steve
The text was updated successfully, but these errors were encountered: