You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basic idea code (which also works) is available in release v0.1.2 under system_host folder. The logic is as follows
cookie secret is generated (needs to be given by the user?)
There's a permanent database which holds information about the credentials and a SQLite in memory database which holds a login entry after the given credentials are validated
necessary headers are set and credentials are verified for each request
Possible steps
Integrate this logic , the separated branch has only started the integration, but not completed
Write a dataclass or similar, which will accept information from the user what are the credentials
For each property, action and event, support separate credentials. By default, the Thing level credential must be supported for each property, action and even, but can be fine-tuned on case by case basis
Update TD generation logic to add information about security schemes, including interaction affordance specific security
Add a flag at class level allow_unauthorized_access, which has to be set to False if a HTTP server will be used. This should be the default behaviour to force the user to think about security.
Add tests
Same may be done for another security method as well. I do not know how to code other security schemes.
The text was updated successfully, but these errors were encountered:
To authenticate access to the hardware through HTTP, cookie auth needs to be added.
A separate branch has already been created for this.
Basic idea code (which also works) is available in release v0.1.2 under system_host folder. The logic is as follows
Possible steps
Thing
level credential must be supported for each property, action and even, but can be fine-tuned on case by case basisallow_unauthorized_access
, which has to be set to False if a HTTP server will be used. This should be the default behaviour to force the user to think about security.Same may be done for another security method as well. I do not know how to code other security schemes.
The text was updated successfully, but these errors were encountered: