blob: e014843a713092492b3ac8857b4ce6248be141d7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
# Access tokens
Access tokens are created tokens that enable "secret URLs" with access
to specific information from the conference.
This can for example be live-pulling data into a Google spreadsheet,
or consuming it from a JavaScript based schedule webpage, or any
other interesting ideas people can come up with.
The idea between the specific access token objects is that each
individual service that uses this should be given a separate
token. This way it becomes possible to revoke a token for just one
such consumer without shutting down all the others.
### Reference
The access token objects have the following fields:
Token
: This is the secret URL token. It's automatically filled with random
data when a new token is created, and it cannot be changed.
Description
: Internal description. This is not used by the system anywhere, it's
just for administrators to know what is what.
Permissions
: This list the different kinds of access that can be retrieved using
this token. For each access type it will also have a csv (comma
separated), tsv (tab separated) and json values link that includes the
token. (More formats may be added in the future).
### Attached files
Some token URLs, in particular the sponsor claimed benefits one, also
supports attached files. In this case, append the return suburl from
the system (that is in the file behind the normal token link) to the
end of the URL and make a separate request for that.
|
