Update cloud-events.md #208
Conversation
added consi cloud events
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
| @@ -286,6 +286,29 @@ The application then may get the latest terms of use through the [Get Terms Of U | |||
| } | |||
| ``` | |||
|
|
|||
| ## Consent update events | |||
|
|
|||
| Fired whenever a user grants or revokes a consent. A whole deletion of a consent triggers a revoked event. | |||
There was a problem hiding this comment.
I suggest to remove the word "whole".
| ## Consent update events | ||
|
|
||
| Fired whenever a user grants or revokes a consent. A whole deletion of a consent triggers a revoked event. | ||
| Applications that are part of any of the users subscriptions receive a notification. The application can then retrieve the latest consense status of the user. |
There was a problem hiding this comment.
"Application is part of users subscription" ? Unclear what you mean.
A subscription can have a license of an application.
"users subscription" means I guess "user's subscription"
Further: get the consent information, such as consented scope, from the Consent API.
Where we need to add the "Consent API" to https://developer.tapio.one/general/available-apis when APIM story is implemented.
| Fired whenever a user grants or revokes a consent. A whole deletion of a consent triggers a revoked event. | ||
| Applications that are part of any of the users subscriptions receive a notification. The application can then retrieve the latest consense status of the user. | ||
|
|
||
| `tapio.consentinator.consent.revoked` |
There was a problem hiding this comment.
The cloud event type should not expose any reference to internal services. The event type should start with one.tapio.selfservice.
There was a problem hiding this comment.
According to our discussions in the integration meeting, start should be tapio.selfservice
See internal docs.
added consi cloud events