Skip to content

Improve identity management for rate limiting #8954

@netomi

Description

@netomi

Currently we use the following as key for identities:

  • access-token: hash of the token
  • session: session id
  • ip range: customer id

However it was noted that we should rather use the user id in case an access token / session is identified.

Metadata

Metadata

Assignees

Labels

team:software-devIssues that requires support from the Eclipse Foundation software-dev team

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions