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
This is a tenant or application scoped event. It can be sent to all applications in a tenant or to one or more specified applications.
2
+
3
+
The ability to limit the generation of an event for only certain applications is legacy functionality and may be modified in the future. You almost certainly want to enable this event at the tenant level and optionally filter on the `applicationId` when consuming the event.
Copy file name to clipboardExpand all lines: site/docs/v1/tech/events-webhooks/events.adoc
+80-11Lines changed: 80 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -27,13 +27,21 @@ These are the events that FusionAuth generates that can be optionally consumed b
27
27
* <<JWT Refresh>> - when an access token is refreshed using a refresh token
28
28
* <<JWT Refresh Token Revoke>> - when a refresh token (or multiple tokens) are revoked
29
29
30
+
=== Tenant Scoped Events
31
+
32
+
Tenant scoped events are generated for all applications in a tenant or for none of them.
33
+
34
+
All user events are tenant scoped because a user is a tenant scoped entity. For example, the `user.delete`, `user.create`, `user.update`, and `user.deactivate` events are all tenant scoped.
35
+
36
+
A tenant scoped event can, however contain an `applicationId` which can be used to filter events when received. One example is `user.registration.create`.
37
+
30
38
=== Application Scoped Events
31
39
32
40
A few events can be generated for one or more specified applications, or for all applications within a tenant.
33
41
34
42
[WARNING]
35
43
====
36
-
The ability to limit the generation of an event for only certain applications is legacy functionality and may be modified in the future. You almost certainly want to use a tenant scoped event and optionally filter on the `applicationId` when consuming the event.
44
+
The ability to limit the generation of an event for only certain applications is legacy functionality and may be modified in the future. If you want to get events for certain applications, send events for a tenant. Filter on the `applicationId` when consuming the event and discard events from any applications that are not of interest.
37
45
====
38
46
39
47
These events can be application scoped:
@@ -42,16 +50,6 @@ These events can be application scoped:
42
50
* `jwt.refresh-token.revoke`
43
51
* `user.action`
44
52
45
-
=== Tenant Scoped Events
46
-
47
-
Any events which are not application scoped events are tenant scoped.
48
-
49
-
Tenant scoped events can't be limited to fire only for a certain application. These events are either generated for all applications in a tenant or for none of them.
50
-
51
-
All user events are tenant scoped because a user is a tenant scoped entity. For example, the `user.delete`, `user.create`, `user.update`, and `user.deactivate` events are all tenant scoped.
52
-
53
-
A tenant scoped event can, however contain an `applicationId` which can be used to filter events when received. One example is `user.registration.create`.
54
-
55
53
== User Actions
56
54
57
55
This event is generated when a User Action is taken on a user and when temporal actions transition between phases.
@@ -64,6 +62,10 @@ A temporal action is one that has a start time and and a duration, when a phase
0 commit comments