Skip to content

LRU based cache for JWT #4003

@taimoorzaeem

Description

@taimoorzaeem

Problem

Our current JWT cache implementation has no upper bound for number of cache entries. This can cause OOM errors. Additionally, the purge mechanism for expired entries is quite slow.

Solution

Switch to lrucache implementation for limited number of cache entries. We'll need a new config option (say jwt-max-cache-entries) for this to work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    authnRelated to authenticationbreaking changeA bug fix or enhancement that would cause a breaking change

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions