-
Notifications
You must be signed in to change notification settings - Fork 4
/
666.txt
124 lines (90 loc) · 4.86 KB
/
666.txt
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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
* 仕様書
[REFS[
- [17] [CITE@en[[[RFC 7519]] - JSON Web Token (JWT)]], [TIME[2019-11-25 08:15:37 +09:00]] <https://tools.ietf.org/html/rfc7519>
- [18] [CITE[RFC Errata Report » RFC Editor]], [TIME[2019-12-06 11:32:15 +09:00]] <https://www.rfc-editor.org/errata_search.php?rfc=7519>
- [16] [CITE@en[[[RFC 7797]] - JSON Web Signature (JWS) Unencoded Payload Option]], [TIME[2019-11-27 04:23:28 +09:00]] <https://tools.ietf.org/html/rfc7797>
]REFS]
* 文脈
[FIG(short list)[ [15] [[JWT]] の[[応用]]
- [[VAPID]]
- [CODE[jwtTokenString:]]
- [[SCIM]]
]FIG]
* 関連
[8] [[CBOR]] 版の [[CWT]] もあります。
* 歴史
[1] [CITE@en[draft-ietf-oauth-json-web-token-32 - JSON Web Token (JWT)]]
([TIME[2015-01-13 11:57:47 +09:00]] 版)
<https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32>
[2] [CITE@en[draft-ietf-oauth-jwt-bearer-12 - JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants]]
([TIME[2015-01-13 05:24:39 +09:00]] 版)
<http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-12>
[3] [CITE@en[RFC 7519 - JSON Web Token (JWT)]]
([TIME[2015-05-20 09:55:25 +09:00]] 版)
<https://tools.ietf.org/html/rfc7519>
[4] [CITE@en[RFC 7521 - Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants]] ([TIME[2015-05-28 13:43:35 +09:00]] 版) <https://tools.ietf.org/html/rfc7521>
[5] [CITE@en[RFC 7523 - JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants]] ([TIME[2015-05-28 13:43:53 +09:00]] 版) <https://tools.ietf.org/html/rfc7523>
[6] [CITE@en[RFC 7800 - Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)]]
([TIME[2016-04-14 20:45:18 +09:00]] 版)
<https://tools.ietf.org/html/rfc7800>
[FIG(quote)[
[FIGCAPTION[
[7] [CITE@en[Volkswagen Infotainment Web Interface protocol definition]]
([TIME[2016-12-24 01:55:51 +09:00]])
<https://www.w3.org/Submission/2016/SUBM-viwi-protocol-20161213/>
]FIGCAPTION]
> JWT tokens will be sent in the Authorization header, following with term JWT and a space character.
> Example that assumes eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSm9obiBEb2UifQ.xuEv8qrfXu424LZk8bVgr9MQJUIrp1rHcPyZw_KSsds is the actual token:
> GET /<service>/<resource> HTTP/1.1
> Host: 127.0.0.1:1337
> Authorization: JWT eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSm9obiBEb2UifQ.xuEv8qrfXu424LZk8bVgr9MQJUIrp1rHcPyZw_KSsds
>
]FIG]
[9] [CITE[Stop using JWT for sessions - joepie91's Ramblings]]
( ([TIME[2016-08-16 04:42:57 +09:00]]))
<http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-for-sessions/>
[10] [CITE[Stop using JWT for sessions, part 2: Why your solution doesn't work - joepie91's Ramblings]]
( ([TIME[2016-08-16 04:42:57 +09:00]]))
<http://cryto.net/~joepie91/blog/2016/06/19/stop-using-jwt-for-sessions-part-2-why-your-solution-doesnt-work/>
[FIG(quote)[
[FIGCAPTION[
[11] [CITE@en[Mapbox API Documentation]]
([TIME[2017-05-10 01:21:59 +09:00]])
<https://www.mapbox.com/api-documentation/#the-token-format>
]FIGCAPTION]
> Mapbox uses JSON Web Tokens (JWT) as the token format.
]FIG]
[FIG(quote)[
[FIGCAPTION[
[12] [CITE@ja[HipChat - API v2 - Webhooks]]
([TIME[2017-05-25 23:20:57 +09:00]])
<https://www.hipchat.com/docs/apiv2/webhooks>
]FIGCAPTION]
> Webhooks declared by an add-on can optionally receive a JWT authenticating the request. The JWT is sent in the Authorization header and has the same structure as the JWT sent in the signed_request query parameter for configuration pages and other UI elements:
> POST /echo HTTP/1.1
> Host: addon.example.com
> Authorization: JWT eyJhbGciOiAiSFMyNTYiLCAi...
> Content-Length: 646
> Content-Type: application/json
]FIG]
[FIG(quote)[
[FIGCAPTION[
[13] [CITE[Bitbucket API]]
([TIME[2017-09-08 16:52:25 +09:00]])
<https://developer.atlassian.com/bitbucket/api/2/reference/meta/authentication>
]FIGCAPTION]
> 5. Bitbucket Cloud JWT Grant (urn:bitbucket:oauth2:jwt)
> If your Atlassian Connect add-on uses JWT authentication, you can swap a JWT for an OAuth access token. The resulting access token represents the account for which the add-on is installed.
> Make sure you send the JWT token in the Authorization request header using the "JWT" scheme (case sensitive). Note that this custom scheme makes this different from HTTP Basic Auth (and so you cannot use "curl -u").
> $ curl -X POST -H "Authorization: JWT {jwt_token}" \
> https://bitbucket.org/site/oauth2/access_token \
> -d grant_type=urn:bitbucket:oauth2:jwt
]FIG]
[FIG(quote)[
[FIGCAPTION[
[14] [CITE[Features | Netlify]]
([TIME[2017-10-09 14:29:02 +09:00]])
<https://www.netlify.com/features/>
]FIGCAPTION]
> With JWT Based Access Control you build sites with any site generator and enable granular role based permissions while delegating authentication and user management to any service that can issue JSON Web Tokens.
]FIG]