I più scaricati: Dati aggiornati al 27 ottobre 2026

Categorie

Internet1356
Comunicazione321
Audio e video898
Grafica e design539
Ufficio e produttività1124
Strumenti di sviluppo3134
Strumenti di IA529
Sicurezza e privacy385
Strumenti di sistema3114
Giochi523
Istruzione e scienza239
Rete e IT284

openapi-oathkeeper: versioni precedenti da scaricare

Generate Ory Oathkeeper access rules from an OpenAPI 3 contract.

Qui sono elencate 4 versioni di openapi-oathkeeper, dalla prima (19 marzo 2026) fino all’attuale 0.8.0. Ognuna rimanda ai file di installazione del produttore.

2026: 4 4 26
VersioneDataDimensioneFile
0.8.0Ultima versione 9 settembre 2026 — 64 bit ZIP32 bit ZIP
Note di rilascio
## What's Changed

• Add integration tests by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/143
• feat:update dependencies and image version by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/144
• Capture array and object path params as explicit types by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/145

**Full Changelog**:https://github.com/cerberauth/openapi-oathkeeper/compare/v0.7.19...v0.8.0
0.7.19 7 settembre 2026 — 64 bit ZIP32 bit ZIP
Note di rilascio
## Security fix

**High severity:** Overbroad path-parameter regex in generated Ory Oathkeeper access rules could cause an authentication/authorization bypass.

Previously, every OpenAPI `string` path parameter (and any parameter type the generator couldn't classify) was compiled to the unanchored regex token `<.+>`. Because `.` matches `/` in Go's regexp engine — and in Ory Oathkeeper's `regexp` matching strategy — a rule generated for a single path segment (e.g. `/public/{slug}`) also matched deeper, unrelated paths under the same prefix (e.g. `/public/admin/delete-all-users`). If those deeper paths weren't defined as their own, more specific OpenAPI operations, the broader (often unauthenticated `noop`) rule would match and proxy them instead of being rejected.

Generated rules for `string` and unclassified path parameters now use `<[^/]+>`, anchored to a single URL segment, matching the behavior already documented for numeric parameters.

**Action required:** Regenerate your Ory Oathkeeper access rules with this version and redeploy them. Rules generated by earlier versions using `string` path parameters may be broader than intended.

See [GHSA-9f3w-vm54-7gfc](https://github.com/cerberauth/openapi-oathkeeper/security/advisories/GHSA-9f3w-vm54-7gfc) for full details. Thanks to @EQSTLab for the responsible disclosure.

## What's Changed

• fix(generator):anchor string path-parameter regex to a single URL segment by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/142

**Full Changelog**:https://github.com/cerberauth/openapi-oathkeeper/compare/v0.7.18...v0.7.19
0.7.18 13 agosto 2026 — 64 bit ZIP32 bit ZIP
0.7.15 19 marzo 2026 — 64 bit ZIP32 bit ZIP

Il più popolare in Linguaggi e SDK

Vedi tutti
  1. LLVMLinguaggi e SDK · LLVM
  2. DenoLinguaggi e SDK · Deno Land Inc.
  3. CMakeLinguaggi e SDK · Kitware
  4. YarnLinguaggi e SDK · Yarn Contributors
  5. CcacheLinguaggi e SDK · Joel Rosdahl
  6. sbtLinguaggi e SDK · Lightbend, Inc.
  7. BOINCLinguaggi e SDK · Space Sciences Laboratory, U.C. Berkeley
  8. Dart SDKLinguaggi e SDK · Google
  9. NVM for WindowsLinguaggi e SDK · Ecor Ventures LLC

Altri programmi di CerberAuth

Vedi tutti
  • jwtopLinguaggi e SDK · CerberAuth

Condividi