Skip to content

chore: read JWT keys from config

What does this merge request do and why?

JWT_SIGNING_KEY and JWT_VALIDATION_KEY are implicitly used in AI Gateway as the application settings.

We introduced AIGW_SELF_SIGNED_JWT__SIGNING_KEY and AIGW_SELF_SIGNED_JWT__VALIDATION_KEY as replacements.
We need to read them properly via config instead of accessing ENV vars directly from the API implementation.

How to set up and validate locally

We need to re-check that the endpoint v1/code/user_access_token still works.

So we need to follow:
!796 (merged)

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.

Closes #482 (closed)

Edited by Aleksei Lipniagov

Merge request reports