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: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,8 @@ The token consists of two parts. Firstly, a header containing non-sensitive meta
13
13
"ti": "159aba3e-55e1-4f54-b6ee-e5b943d7e885”,
14
14
"c": "ticketania",
15
15
"e": "demoevent”,
16
-
"ip": "75.86.129.4"
16
+
"ip": "75.86.129.4",
17
+
"xff": "45.67.2.4,34.56.3.2"
17
18
}
18
19
```
19
20
-`typ`: The type of the token. Value must be “QFT1”. Required.
@@ -23,7 +24,8 @@ The token consists of two parts. Firstly, a header containing non-sensitive meta
23
24
-`ti`: Unique Token ID (e.g. uuid). Used to uniquely identify tokens and restrict replay attacks. Required.
24
25
-`c`: The Customer ID of the issuer. Token will only be valid on events on this account. Required.
25
26
-`e`: The Event ID. If provided, token will only be valid on this event. Optional.
26
-
-`ip`: The IP address the user the token is issued to. If provided, token will only be valid for this IP address. Optional.
27
+
-`ip`: The IP address the user the token is issued to. If provided, the IP address is validated before issuing the token. Optional.
28
+
-`xff`: The X-Forwarded-For headerof the request when the token is issued. If provided, the X-Forwarded-For header is validated before issuing the token. Optional.
0 commit comments