-
Notifications
You must be signed in to change notification settings - Fork 18
role of server side clients #9
Comments
from @dmitrizagidulin on a call
|
Noting what Demitri said in the community meeting: such an app would use oidc hybrid flow: Where Given we're going to implement client ids to distinguish web apps (#12), acl:trustedApp will reference the token just like any other flow. |
Just to clarify few things and match names used in diagram to terminology from Decentralized Authentication Glossary Presenter X and Presenter Y act as: Bot X and Bot Y act as:
RS/RP Alice's, Bob's and ACME's act as
I don't know if we can also consider confidential client (Alice's Bot X) as presenter but it will use credentials from Alice's OP to access ACME's RS/RP
If all the clients (Presenter X & Y, Bot X & Y) use PoPToken they also seem to act as RP. In my diagram only OPs don't act as RPs |
cc @sylvainlb about server-side clients |
This relates to: https://forum.solidproject.org/t/push-notifications-push-api/1079
I can see use for all kinds of clients which run 'in the cloud' rather than on local devices in web browsers. In example below Alice and Bob use two different applications running on their devices and to my understanding acting as Presenters. But each of those application has companion client running on some server 'in the cloud' which in this case sends Push notifications to the applications running on local devices. For the sake of discussing it I just call them bots on diagram below.
Few things I see need to clarify
acl:trustedApp
and Origin restrictionsIn illustration above Alice and Bob might want to get notifications caused by writes of the other one to the acme RS/RP. We can't really rely on Solid Websockets API since mobile OS will not keep all the applications active. Push Notifications and Service Workers already address this issue we just need a clear way to integrate that solution. Each application (running on the device) might provide their own bot that could subscribe to Websockets API and send customized push notifications to the app it accompanies.
The text was updated successfully, but these errors were encountered: