search

iiitd-ucla-pc3 / SensorActApp

2 stars 1 forks source link

Guard rule UI modification for the owner #12

Open manaswisaha opened 11 years ago

manaswisaha commented 11 years ago

What modifications on the UI required when owner wants to create a guard rule? The older interface specified the username/email of the user as conditions (to give them access to his/her devices). The new architecture allows the VO to create guard rules and their associations on-the-fly. So what should the explicit guard rule UI take as inputs?

amarjeet-iiitd commented 11 years ago

We need to think a little on this

My feeling is that the guard rule interface should be provided as the VO is logged on to the broker (currently the share devices interface). There should not be a way to directly make any guard rule on the VPDS interface (this is because if the user does not register the VPDS on broker then anyway its only VO who has access to VPDS and no other user has access).

On Thu, Feb 21, 2013 at 1:44 PM, Manaswi Saha notifications@github.comwrote:

What modifications on the UI required when owner wants to create a guard rule? The older interface specified the username/email of the user as conditions (to give them access to his/her devices). The new architecture allows the VO to create guard rules and their associations on-the-fly. So what should the explicit guard rule UI take as inputs?

— Reply to this email directly or view it on GitHubhttps://github.com/iiitd-ucla-pc3/SensorActApp/issues/12.

Best Regards

Amarjeet Singh, Asst. Professor, IIIT Delhi http://www.iiitd.edu.in/~amarjeet/

manaswisaha commented 11 years ago

Yes, that is true. So then I will disable everything related to the creation of guard rules (and their associations) on the VPDS. Would that be fine?

amarjeet-iiitd commented 11 years ago

I dont understand.

Guard rules will still still be be created at the VPDS.

The broker will expose a set of users that are registered with the broker. As the VO shares specific privileges with another user, those privileges together with the corresponding key get stored in the VPDS (and probably in the broker as well as in your current architecture).

Let us discuss this in person next week.

On Sat, Feb 23, 2013 at 2:56 PM, Manaswi Saha notifications@github.comwrote:

Yes, that is true. So then I will disable everything related to the creation of guard rules (and their associations) on the VPDS. Would that be fine?

— Reply to this email directly or view it on GitHubhttps://github.com/iiitd-ucla-pc3/SensorActApp/issues/12#issuecomment-13987481.

Best Regards

Amarjeet Singh, Asst. Professor, IIIT Delhi http://www.iiitd.edu.in/~amarjeet/

manaswisaha commented 11 years ago

I apologize for being unclear earlier. What I meant by disabling is disabling the guard rules creation UI, not the backend process. The VPDS will still create guard rules on the fly. I will disable the UI for explicit creation of guard rules