A frontend compatible with SAI Authorization Agent Service, the two together provide a compliant Authorization Agent implementation.
The frontend uses Solid-OIDC to authenticate with the backend. It also provides OIDC Provider to the backend and takes care of redirecting the user to authenticate the backend.
Push API is used to receive notifications from the backend. Currently, it's only being used when the initial Access Receipt arrives from another social agent and the user gets prompted to create a Social Agent Registration for them. Verifying the identity of that social peer is a high-priority next step on the SAI agenda.
The frontend uses api-messages to control the backend based on the user's interactions.
- List all the Applications based on existing Application Registrations
- Authorize a new Application, this is initiated by a redirect from the application.
- List all the Social Agents based on existing Social Agent Registrations
- Add a new social peer connection by creating a new Social Agent Registration, this is initiated by receiving a Push Notification from the backend, based on an Access Receipt it received.
- List all the Data Registries and all the Data Registrations in them.
- SRV_BASE - the root for the SAI Authorization Agent Service
- OIDC_CLIENT_ID - the Solid-OIDC Client ID Document can be hosted independently
- DEFAULT_IDP: - the default Solid-OIDC Provider
- VAPID_PUBLIC_KEY - public key from a keypair used by the backend to send Push Notifications
This project was generated with Angular CLI version 13.2.0.
Run yarn start for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
ng serve doesn't work with push notifications. You can follow Web Push Notification with web-push | Angular & Node JS to see how to test them locally.