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
Copy file name to clipboardExpand all lines: src/pages/controller/native/session-flow.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,5 +86,19 @@ After successful session creation, the following metadata is available:
86
86
|`appId`| string? | The application identifier |
87
87
|`isRevoked`| boolean | Whether the session has been revoked |
88
88
89
+
### Additional Fields for Already-Registered Sessions
90
+
91
+
When a session is already registered and authorized, the callback payload includes additional session identifiers:
92
+
93
+
| Field | Type | Description |
94
+
|-------|------|-------------|
95
+
|`allowedPoliciesRoot`| string | Root hash of the allowed policies for this session |
96
+
|`metadataHash`| string | Hash of the session metadata |
97
+
|`sessionKeyGuid`| string | Unique identifier for the session key |
98
+
|`guardianKeyGuid`| string | Unique identifier for the guardian key |
99
+
|`alreadyRegistered`| boolean | Flag indicating this is an existing session |
100
+
101
+
These fields are only included when returning an existing authorized session (when `alreadyRegistered` is `true`). For new session registrations, only the basic metadata fields are returned.
102
+
89
103
Fields marked with `?` are only populated when creating sessions via the subscription API flow (`createFromSubscribe`).
90
104
When creating sessions directly with the constructor, these fields will be `null`.
0 commit comments