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: docs/EXISTING_SITES.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,16 @@ This guide describes how to add AgeCheck to an existing adult website without re
9
9
3. Redirect unverified users to your gate route (for example `/ageverify`).
10
10
4. Verify JWT at `POST /verify`, set signed HttpOnly cookie, redirect back.
11
11
12
+
## Existing Gate Integration (Provider Mode)
13
+
14
+
If your site already has a gate and multiple providers, add AgeCheck as one provider option:
15
+
16
+
1. Keep your gate UI and policy engine unchanged.
17
+
2. Generate or forward the provider session identifier (AgeCheck expects `agegateway_session`).
18
+
3. For AgeCheck, call `verifyAgeCheckCredential(...)`.
19
+
4. For other providers, map result with `normalizeExternalProviderAssertion(...)`.
20
+
5. Issue one canonical cookie with `buildSetCookieFromProviderAssertion(...)`.
21
+
12
22
## Why this pattern
13
23
14
24
- enforcement remains server-side
@@ -33,7 +43,18 @@ Set with:
33
43
34
44
## Provider coexistence
35
45
36
-
If you support more than one verifier, normalize each verification result into the SDK `VerificationAssertion` shape and reuse the same signed-cookie issuance and enforcement logic.
46
+
If you support more than one verifier, normalize each verification result into the provider assertion shape and reuse the same signed-cookie issuance and enforcement logic:
0 commit comments