@lucaapp/service-utils 5.29.0 → 5.29.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/lib/api/openapi.js +8 -0
- package/package.json +1 -1
package/dist/lib/api/openapi.js
CHANGED
|
@@ -233,6 +233,14 @@ options, tags, debug) => {
|
|
|
233
233
|
let querySchema = options.schemas?.query || undefined;
|
|
234
234
|
let headersSchema = options.schemas?.headers || undefined;
|
|
235
235
|
let responseSchemas = options.responses;
|
|
236
|
+
// Union across middlewares, one scheme per requirement object, which OpenAPI
|
|
237
|
+
// reads as "any one of these". Deliberately not one object holding all of
|
|
238
|
+
// them, which would read as "all of these at once": jwt_operator,
|
|
239
|
+
// jwt_support, jwt_operator_device and jwt_consumer are all apiKey in the
|
|
240
|
+
// same X-Auth header, so requiring two of them is unsatisfiable. Nearly every
|
|
241
|
+
// location-guarded route stacks requireOperatorOROperatorDevice with
|
|
242
|
+
// authorizeLocation(Group), and 5.29.1 documented those 281 routes as needing
|
|
243
|
+
// an operator token and an operator-device token simultaneously.
|
|
236
244
|
const securitySchemes = new Set();
|
|
237
245
|
if (options.errors) {
|
|
238
246
|
for (const errorType of Object.keys(options.errors)) {
|