Chose a particular security schema for an ExposedThing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
As referred in https://github.com/w3c/wot-scripting-api/pull/289#issuecomment-775182073:
- Applications should avoid entirely providing securityDefinitions
- They (applications) may choose a particular definition using the schema field (globally or at form level)
This issue keeps track of how it would be possible to choose a particular scheme at the application level. One possible solution would be the definition of a proper function that lists all the possible SecurityScheme supported by a particular protocol binding and the runtime.
listSupportedSchemas(): Map<Protocol,SecuritySchemaDefinition[]>
Where Protocol could be the protocol URI scheme (i.e., HTTP,mqtt, ... )
However, I'm sure if it might have some security implications (fingerprinting?).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PR #289 comment referenced by this issue and review the proposed listSupportedSchemas signature. Evaluate application-level selection of a SecurityScheme at global or form level, including the stated fingerprinting concern. Done means an application-level approach is agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100