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
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
//! Who is making this request (issue #153).
//!
//! A module that serves a row belonging to somebody has to know who is
//! asking. Nothing in the harness could answer that: the verifier lives
//! in `cratefield-auth-client`, whose extractor needs `AuthState` in the
//! router state, and a module's state is an `Arc<ModuleContext>`. So a
//! module could check an admin token or nothing at all.
//!
//! This is the port that closes it. A deployment wires one; a module
//! declares [`Port::Auth`](super::Port::Auth) and gets it, and a module
//! that declares it cannot be composed into a deployment that has none —
//! which is the guarantee worth having. A venture declaring a table whose
//! access is `owner` composes a module that requires this port, so the
//! deployment refuses to boot rather than serving that table to everyone.
//!
//! # An unverified credential is not anonymity
//!
//! [`Auth::identify`] answers `Ok(Caller::Anonymous)` only when the
//! request carried no credential at all. A credential that was presented
//! and did not verify is an error, always, even for a route that would
//! have served an anonymous caller.
//!
//! The alternative — folding a bad token into "anonymous" — is a hole
//! with no floor. An expired token reading a `public-read` table would
//! succeed, so nothing would tell the caller their session had ended;
//! and the first handler written to fall back to anonymous on error
//! would hand anonymous access to anybody presenting a forged token. The
//! distinction has to survive as far as the handler, so it is in the
//! type.
use Arc;
use async_trait;
use HeaderMap;
/// The person a verified credential speaks for.
/// Who the request is from.
/// Why a caller could not be identified.
///
/// Two cases and they are not the same refusal: one is the caller's
/// problem and one is the deployment's, so one is a 401 and the other a
/// 503. Collapsing them would tell a user to sign in again while the auth
/// service is down, and they would, and it would not help.
/// Turns a request's headers into the caller they speak for.
///
/// Headers rather than an extractor so the port is object-safe and can be
/// exercised without an HTTP stack; the extractor is built on top.
/// The verifier a deployment gets when it asked for one from the
/// environment and the environment did not have it.
///
/// A **provided port that verifies nothing**, the same shape
/// `push_from_env` uses for a push router with no transports configured:
/// on Workers the `Env` exists per request, so a runtime cannot know at
/// compose time whether the issuer is set, and refusing to provide the
/// port would make every such deployment fail to boot — including the
/// ones whose tables are all public and never need it.
///
/// What it answers is chosen so nothing reads as working:
///
/// - **no credential** is [`Caller::Anonymous`], so a `public-read` table
/// still serves and a deployment that only publishes is unaffected;
/// - **a credential** is [`AuthError::Unavailable`], never `NotVerified`
/// — the token may be perfectly good and nothing here can tell, so
/// saying it did not verify would be a claim this has not established.
///
/// A table whose access needs a caller therefore answers 401 to an
/// anonymous request and 503 to a signed-in one, and the boot warning
/// naming the missing variables is in the log either way.