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
In the four-party setup discussed in #33, the main AS will have a list of grants to revoke, and each helper needs to at least have a way to display individual "shares" (see #33 for naming discussion), so it's likely to also have a list view of them, and possibly also revoke buttons there. This is especially true if the helper GUI is integrated with the RS GUI.
Maybe this is OK, because the main AS lists all grants, and the helpers list only their own shares, and they probably cannot list the client IDs.
When you revoke all grants that rely on a share, it's OK for the share to still exist.
But if you revoke a share, it would be nice to see the grants also disappear from the main AS. Do we need a protocol for that?
The text was updated successfully, but these errors were encountered:
In the four-party setup discussed in #33, the main AS will have a list of grants to revoke, and each helper needs to at least have a way to display individual "shares" (see #33 for naming discussion), so it's likely to also have a list view of them, and possibly also revoke buttons there. This is especially true if the helper GUI is integrated with the RS GUI.
Maybe this is OK, because the main AS lists all grants, and the helpers list only their own shares, and they probably cannot list the client IDs.
When you revoke all grants that rely on a share, it's OK for the share to still exist.
But if you revoke a share, it would be nice to see the grants also disappear from the main AS. Do we need a protocol for that?
The text was updated successfully, but these errors were encountered: