Difference between revisions of "Reasoners security from service"
From AMTech WikiDocs
| Line 1: | Line 1: | ||
THIS OPTION IS DISABLED AT THE MOMENT | THIS OPTION IS DISABLED AT THE MOMENT | ||
| + | |||
Security from service will be used for executing the observer and actions | Security from service will be used for executing the observer and actions | ||
* Observer will observe things shared with the tenant (not only the things owned by the tenant as it is the case for reasoner with security from observation) | * Observer will observe things shared with the tenant (not only the things owned by the tenant as it is the case for reasoner with security from observation) | ||
Revision as of 13:43, 23 July 2018
THIS OPTION IS DISABLED AT THE MOMENT
Security from service will be used for executing the observer and actions
- Observer will observe things shared with the tenant (not only the things owned by the tenant as it is the case for reasoner with security from observation)
- Access policies to types are not enforced when executing actions. All actions performed by the topology will use the list of tenants subscribed to the service as only authorization info, so for accessing the resources, tenants and guest tenants will be checked against the list of tenants subscribed to the service, but types won't be checked since there is no info of actors available for a service.
Expected Behaviors
- A follower that is not able to create/update/delete a resource of a certain type, because he does not have the actors, will be able to do so by pushing an observation that triggers a reasoner with security from the service that creates/updated/deletes a resource of that type. (the execution of the action in the topology runs behind the service, thus, the tenants subscribed to it, without any specific user, thus no specific actors)
