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

Clarify whether security is mandatory #230

Closed
mmccool opened this issue Sep 12, 2018 · 3 comments
Closed

Clarify whether security is mandatory #230

mmccool opened this issue Sep 12, 2018 · 3 comments

Comments

@mmccool
Copy link
Contributor

mmccool commented Sep 12, 2018

Currently all "security" fields are "optional" which is confusing since in fact the rule is that security is necessary at "at least one level". Matthias suggested a way around this would be to make the top-level security mandatory and the rest at lower levels (eg in forms) optional. In effect the top level would define the "default" value of the security field, then it is overridden only for exceptions.

@benfrancis
Copy link
Member

I recommend they should all be optional.

@mmccool
Copy link
Contributor Author

mmccool commented Oct 30, 2018

We discussed this at length a while ago and decided the simplest solution was to make them mandatory only at the top level, which avoids a lot of complicated checking, and at worst adds only one line to the TD. To go along with this there is a new "nosec" security scheme, which is needed in the case there is no security.

Somehow my previous edits to make this change did not "stick" so I just created another PR: #265

@sebastiankb
Copy link
Contributor

since a long time, security is a mandatory requirement in the TD. This should increase awareness for IoT applications.
I will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants