Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mapping tuya device #1880

Open
relu91 opened this issue Apr 8, 2022 · 1 comment
Open

Mapping tuya device #1880

relu91 opened this issue Apr 8, 2022 · 1 comment
Labels
Defer to TD 2.0 Has Use Case Potential The use case can be extracted and explained Security Selected for Use Case The issue is relevant for the work and should move to an use case

Comments

@relu91
Copy link
Member

relu91 commented Apr 8, 2022

We are trying to map Tuya devices in node wot (eclipse-thingweb/node-wot#735), but we struggled to fit their authentication mechanism inside the set of Thing Description SecuritySchemes. For the time being, we are opting for a workaround: defining a custom security scheme. However, I would like to understand if the tuya signature algorithm actually fits inside of the BearerSecurityScheme.

Reading the docs it seems that they are using a custom alg (HMAC-SHA256) plus a custom format (no jws or anything else). Do you think is it feasible to describe that algorithm using the regular BearerSecurityScheme but with specific values of alg and format ?
@mmccool
Copy link
Contributor

mmccool commented Sep 25, 2023

I think this needs to move to the TD repo, but labelled with "Security" so the security TF will review it.

@mmccool mmccool transferred this issue from w3c/wot-security Sep 25, 2023
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Sep 25, 2023
@egekorkan egekorkan removed the needs-triage Automatically added to new issues. TF should triage them with proper labels label Oct 18, 2023
@egekorkan egekorkan added Has Use Case Potential The use case can be extracted and explained Selected for Use Case The issue is relevant for the work and should move to an use case labels Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Defer to TD 2.0 Has Use Case Potential The use case can be extracted and explained Security Selected for Use Case The issue is relevant for the work and should move to an use case
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@relu91 @mmccool @ashimura @egekorkan