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
The current light308 demo only shows the case where an access request is granted, following the profiled and dynamic context information conditions.
We need a setup that can change the access status at runtime, for a demo.
TODO
Two things can affect the access conditions:
the profiled employment status
the dynamic "LocatedAt" stream
Design and implement a flow that enables runtime-level changes to the upb-hmas-profiled-context.ttl file. Implement an observe file change functionality that will reflect in the profiledContextRepo from the ContextMgmtVerticle
Design and implement a method to alter the LocatedAtContextStream to periodically pause once for 10 seconds, before having a bout of 3 instances, all 5 seconds apart, where it senses presence. This needs to be complemented by a check and a change in the ContextDomain membership verification functionality (see issue Enable IStream and DStream flow in dynamic ContextDomain membership verification #4 )
Test that both of the above types of changes affect the access result
The text was updated successfully, but these errors were encountered:
Context
The current light308 demo only shows the case where an access request is granted, following the profiled and dynamic context information conditions.
We need a setup that can change the access status at runtime, for a demo.
TODO
Two things can affect the access conditions:
the profiled employment status
the dynamic "LocatedAt" stream
Design and implement a flow that enables runtime-level changes to the
upb-hmas-profiled-context.ttl
file. Implement an observe file change functionality that will reflect in theprofiledContextRepo
from theContextMgmtVerticle
Design and implement a method to alter the
LocatedAtContextStream
to periodically pause once for 10 seconds, before having a bout of 3 instances, all 5 seconds apart, where it senses presence. This needs to be complemented by a check and a change in the ContextDomain membership verification functionality (see issue Enable IStream and DStream flow in dynamic ContextDomain membership verification #4 )Test that both of the above types of changes affect the access result
The text was updated successfully, but these errors were encountered: