Blame
|
1 | # Passport |
||||||
| 2 | ||||||||
|
3 | Passport is the AeThex identity layer. |
||||||
|
4 | |||||||
|
5 | It is designed to give users one consistent identity across AeThex-connected surfaces: games, support, community systems, governance, creator tools, and developer integrations. |
||||||
|
6 | |||||||
| 7 | --- |
|||||||
| 8 | ||||||||
|
9 | ## What Passport Handles |
||||||
|
10 | |||||||
|
11 | - Account identity |
||||||
| 12 | - Authentication |
|||||||
| 13 | - Linked accounts |
|||||||
| 14 | - Public profile context |
|||||||
| 15 | - Roles and permissions |
|||||||
| 16 | - Inventory and locker context |
|||||||
| 17 | - Achievement and progress context |
|||||||
| 18 | - Support identity and ticket routing |
|||||||
| 19 | - Governance eligibility and voting context |
|||||||
|
20 | |||||||
| 21 | --- |
|||||||
| 22 | ||||||||
|
23 | ## Typical Passport Flow |
||||||
|
24 | |||||||
|
25 | 1. User creates or opens Passport. |
||||||
| 26 | 2. User links external identities when needed. |
|||||||
| 27 | 3. An experience, app, or bot requests identity context. |
|||||||
| 28 | 4. AeThex verifies the user and returns approved scoped data. |
|||||||
| 29 | 5. The integration uses only the required information. |
|||||||
|
30 | |||||||
|
31 | --- |
||||||
|
32 | |||||||
|
33 | ## Integration Principles |
||||||
|
34 | |||||||
|
35 | Passport integrations should follow three rules: |
||||||
|
36 | |||||||
|
37 | 1. **Ask for the minimum scope.** |
||||||
| 38 | 2. **Never expose private user data unnecessarily.** |
|||||||
| 39 | 3. **Make disconnect/revoke behavior obvious.** |
|||||||
|
40 | |||||||
| 41 | --- |
|||||||
| 42 | ||||||||
| 43 | ## Related Pages |
|||||||
| 44 | ||||||||
| 45 | - [[Authentication]] |
|||||||
|
46 | - [[Linked-Accounts]] |
||||||
|
47 | - [[Security]] |
||||||
|
48 | - [[Game-Integration]] |
||||||
| 49 | - [[Discord-Integration]] |
|||||||