https://github.com/cipherstash/test-jwks
JSON Web Key Sets for testing
https://github.com/cipherstash/test-jwks
jwt
Last synced: 3 months ago
JSON representation
JSON Web Key Sets for testing
- Host: GitHub
- URL: https://github.com/cipherstash/test-jwks
- Owner: cipherstash
- License: mit
- Created: 2021-02-09T09:36:02.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-07-27T08:22:53.000Z (almost 3 years ago)
- Last Synced: 2025-01-03T22:43:06.057Z (5 months ago)
- Topics: jwt
- Homepage: https://cipherstash.github.io/test-jwks/
- Size: 7.81 KB
- Stars: 0
- Watchers: 11
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Test JSON Web Key Set Provider
_Do not delete_
## What is this for?
When validating an authentication token (JWT) from a valid Identity Provider (IdP), the service (e.g. a Stash Data Service) must first fetch the public keys from the JSON Web Key Set (JWKS).
In testing this is a bit tricky as we generate our own tokens inside the test suite. So, to validate the URL of this repo is set as the JWKS url.
## Files
This repository exposes two JWKS issuers known as issuer-0 & issuer-1.
`jwks.json` files are publicly accessible at `https://cipherstash.github.io/test-jwks/issuer-0/.well-known./jwks.json` and `https://cipherstash.github.io/test-jwks/issuer-1/.well-known./jwks.json` .
The aforementioned files are used as JSON Web Key Sets in testing the `data-service` in the `platform` repo.
The corresponding key ID and `.pem` files are managed in the `platform` repo. Keep in mind that the `.pem` files and key IDs are cryptographically related to the `jwks.json` files, so must be generated together.