Skip to content

Tyk Gateway v5.3.2, Tyk Dashboard v5.3.2
Compare
Choose a tag to compare
@buger buger released this 01 Aug 19:43
v5.3.2
a5719ff
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Fixed

  • Fixed Dashboard Analytics for PostgreSQL

    Resolved an issue in the api/usage endpoint where the Dashboard with PostgreSQL integration returned unfiltered results when one valid tag was used. Corrected the need for duplicating the same parameter as a workaround for filtering by multiple tags. Results are now properly filtered as expected, improving the accuracy and reliability of analytics data.

  • Enhanced Password Reset security

    Modified default OPA rules to prevent unauthorized admins from modifying other admins' passwords, mitigating potential 'rogue admin' behavior. Tyk Dashboard clients using custom OPA rules should update their rule set accordingly. Contact your assigned Tyk representative for assistance.

  • Fixed Universal Data Graph Schema Editor Import Issue

    Resolved an issue in the GQL schema editor for Data Graphs, where users couldn't utilize the 'Import Schema' button. Now, it's possible to import files containing GQL schemas into the Dashboard.

  • Enhanced Dashboard UI language

    Adjusted wording in Tyk's Dashboard UI to ensure inclusivity and clarity, removing any potentially oppressive language.

  • API Template not associated with Tyk Organization

    Fixed an issue where API Templates were not correctly assigned to Tyk Organizations allowing the potential for accidental sharing of secret data between Organizations through use of the incorrect template.

  • Added control over access to context variables from middleware when using Tyk OAS APIs

    Addressed a potential issue when working with Tyk OAS APIs where request context variables are automatically made available to relevant Tyk and custom middleware. We have introduced a control in the Tyk OAS API definition to disable this access if required.

  • Resolved PostgreSQL Dashboard Analytics issue

    Fixed an issue in the api/usage endpoint where Dashboard+Postgres returned unfiltered results with one valid tag, requiring duplication of the parameter as a workaround for multiple tags. Analytics now correctly filter results as expected.

Assets 2
Loading