-
Notifications
You must be signed in to change notification settings - Fork 2
Refactor DeviceCertView #267
Comments
On me |
I haven't managed to find any signs of this view usage by agent other than: |
@rptrchv The certificate retrieval via api.wott.io is needed for #278 and is used in WoTTsecurity/google-core-iot#1. It should probably require token authentication (the same as for listing all devices), but I'm not sure (@vpetersson ?) |
No, public certificates should not require auth, because they are needed for some device-to-device communication. |
None of the consumers of this view (including the ones you mentioned above) uses its branch
Also we need to get rid of |
exactly so. |
Subtask of #216
DeviceCertView
should be split in two, one for IS_API, another for IS_DASH (see branching byif 'format' in request.GET:
). One branch of this code is currently used by agent, another branch is used by Dash. Instead, the part which is used by Dash should be part of Dash.It will also allow us to remove hardcoded urls in
models.Device.get_cert_url()
.The text was updated successfully, but these errors were encountered: