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.

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

List of required Security Schemes #220

Open
egekorkan opened this issue Jun 17, 2022 · 3 comments
Open

List of required Security Schemes #220

egekorkan opened this issue Jun 17, 2022 · 3 comments
Labels
P1 Priority 1 to be discussed (e.g., next week) Profile-1.1 security

Comments

@egekorkan
Copy link
Contributor

I find the list of security schemes to be supported by HTTP profile consumers to be too much. Not even node-wot implements digest for example: https://github.com/eclipse/thingweb.node-wot/blob/24229b3d84fb7973f64528a0364c481b348ddc4d/packages/binding-http/README.md#feature-matrix

@egekorkan
Copy link
Contributor Author

Also, these are duplicated with https://w3c.github.io/wot-profile/#http-baseline-profile-security

@benfrancis
Copy link
Member

benfrancis commented Jul 14, 2022

There is an Editor's Note in that section (which as you say has been duplicated from section 7.2.9 for some reason) which says:

The list of security schemes to include in the HTTP Baseline Profile is still under discussion.

What do you think the list of mandatory security schemes should be for conformant Consumers? Which schemes are well supported?

In #6 I advocated for NoSecurityScheme and OAuth2SecurityScheme which are what WebThings currently uses (see also: #221 (comment)).

@benfrancis
Copy link
Member

@mlagally As far as I know, nobody is currently planning to implement all of the security schemes currently listed in section 6.3. Are Oracle planning to implement all of them (on both the Producer and Consumer side)? If so, are you aware of a second implementation planned as well?

If not, then we have no choice but to reduce this list for WoT Profile 1.0.

@mlagally mlagally added security P1 Priority 1 to be discussed (e.g., next week) labels Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority 1 to be discussed (e.g., next week) Profile-1.1 security
Projects
None yet
Development

No branches or pull requests

3 participants