Skip to content

[Feature]: Plan removal of legacy refresh-token fallback scans #18

@Bccorb

Description

@Bccorb

Problem statement

On lookup miss, refresh validation still scans all active legacy sessions and bcrypt-compares each hash. That’s a sensible compatibility bridge, but we can not migrate away.

Proposed solution

Add telemetry for fallback hits just error logs or something, then remove the fallback.

Alternatives considered

No response

Impact area

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions