-
Notifications
You must be signed in to change notification settings - Fork 9
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
Questions over HomeDeviceQoD #52
Comments
@ShutingQing Please refer to:
This API has been designed with the expectation that the API client has previously obtained a 3-legged access token that gives access to the appropriate scope of this API ( As part of the procedures to obtain an access token, the user and the home network are identified and authenticated (typically using network-based authentication on the telco side, based on the observed public API of the device, which would be the public IP of the home router). Thus, the API request includes an access token associated with the user (standard And the target user device is identified by the internal IP address (ipAddress field in the API request body) of that device in the home network. |
I'm closing this issue since there have been no further comments and it has already been clarified how the user's router and home device are identified. |
Dears, I have a question over this API, may someone know the answer? Can app, the api caller, knows which router is the user's router? Or how should app know the devices that the user is allowed to adjust the bandwidth?
The text was updated successfully, but these errors were encountered: