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
Introduce a new accessor creation method "asEngine()" in the engine library and make
the following code return an accessor with pseudo role "../__/__engine" and pseudo account "__engine"
_p.asEngine().cell().
Token spec
Engine should then return an access token with the following spec:
Role
Subject
box/_engine
{CellURL}#__engine
../__/_engine
{CellURL}#__engine
With these modifications, box install alone can enable engine to access any box-local resource by distributing ACL to grant "__engine" to access that resource.
Is it necessary to accept pseudo-account "__engine" as a "serviceSubject" attribute in the ESC (Engine Service Collection) setting?
Do we need another pseudo-role, pseudo-account "__rule" for event-rule-triggered execution of engine script?
The text was updated successfully, but these errors were encountered:
shimono
changed the title
Support for a preset account "__engine" to be used in "serviceSubject" attribute in ESC
Introduce "_p.asEngine()" method to return an accessor with preset "__engine" accoount and role
Jun 28, 2019
Overview
Introduce a new accessor creation method "asEngine()" in the engine library and make
the following code return an accessor with pseudo role "../__/__engine" and pseudo account "__engine"
Token spec
Engine should then return an access token with the following spec:
With these modifications, box install alone can enable engine to access any box-local resource by distributing ACL to grant "__engine" to access that resource.
Related Core modification
personium/personium-core#431
considerations.
The text was updated successfully, but these errors were encountered: